I'm trying to get an email notification when my "on-premise TFS 2018" receives a new "voluntary feedback".
I already have a "work item notification" that generates an email when a work item status changes, but a "Feedback response" doesn't apply to this rule.
The current subscription is the one in the image
How can I trigger an e-mail on the "new feedback received"?
The statuses of the Feedback Response work item are Active and Closed, you'll need to change your filter so detect the first state in order to receive your notification.
The feedback client pre-fills this value as far as I know and the value will therefore never be empty on the server if the tools are used the way they should.
Related
I have a calendar tool that integrates with Outlook Calendar. To respond to changes on the Outlook side, I subscribe to push notifications. If I miss the first notification of a change, Outlook sends others with ChangeType: 'Missed' and I synchronize with the user's calendar to retrieve the details of the change. However, deleted events do not seem to be included in the sync response.
The documentation suggests that it is possible to get deleted events:
Synchronize and get new, updated, or deleted events in a specified time range from the user's primary calendar (../me/calendarview) or from a different calendar.
There is even a section about deleted events and synchronization.
Deleted events will contain a reason property with the value of "deleted" to indicate a deleted entity. If the event is a recurring master event, you should delete all of the occurrences and exceptions.
'Created' and 'Updated' ChangeTypes work fine.
Am I subscribing incorrectly? Or is this not a feature of the Outlook Calendar API?
Here is the body of my subscription request:
{
'#odata.type': '#Microsoft.OutlookServices.PushSubscription',
'Resource': "https://outlook.office.com/api/v2.0/me/calendars/#{calendar_id}/events",
'NotificationURL': MY_URL,
'ChangeType': 'Created, Updated, Deleted',
'ClientState': 'foo',
'SubscriptionExpirationDateTime': TTL.minutes.from_now.iso8601
}
Using this plugin to send email notifications after all builds complete. Even if I set the trigger to "Always" under the advanced options of the Editable Email Notification plugin, the email is not always sent. It's sent on all failures and the first success after those failures. But not on all build executions. Thoughts on what I may be doing wrong here?
Add all email address in “Project Recipient List“
Click on “Advance Settings”, Go to "Trigger" and Check “Send To” option for “Always”, If it's not “Recipient List”, then Add “Recipient List” and save your job.
I need to send a message in slack at a time set in advance.
Is there a way to do it through the Slack API or do I need to have a script running and checking if it's time to send the message and then send it?
You should be able to create a reminder sending a message to #slackbot
The message should be like:
/remind [#someone or #channel] [what] [when]
Here's some examples:
/remind #username to do something in 24 hours
or:
/remind #username to do something at 16:00
You can use this free Slack application to send scheduled and self-destruct messages.
https://timy.website
Sending a scheduled message
/send Happy birthday at 12am
/send Happy birthday in 1h30m
Sending a self-destruct message
/delete Secret message! at 2pm
/delete Secret message! in 3h
You can find more details on the website.
If you just want to send a short message to a user at a given time you can use the build-in reminder. The reminder.add method allows you to specify a date, time, message text and the user to receive the message.
The reminder message will appear in the "Slackbot" channel of the addressed user.
Here is an example on how it would look like:
Update April 2019:
There is now a new API method that allows you to submit message for later sending. Its called chat.scheduleMessage.
You can use the official slack api at endpoint chat.postMessage with a key post_at to have your message scheduled. More information in official slack documentation https://api.slack.com/messaging/scheduling. You can also use 3rd party applications, which are free most of the time, for example https://thetopchat.com/ and schedule your message with commands like, for example:
/delay in 3 hours {your message here}
or
/schedule tomorrow at 3pm {your message here}
The Slack API now provides a dedicated endpoint for that. You will need the chat:write scope and the docs say:
Schedules a message to be sent to a channel.
I just implemented it and works as expected.
You can check the docs here: chat.scheduleMessage
I'm currently making a TODO app and I save the date that the user has to do a thing. Let's say that he saves the date 28-7-2016 to do something, I make another column tobenotified and I take the date minus it by 1 and save it, so the user should be notified the previous day that tomorrow has a thing to do.
But what if the user has closed the app(killed it). What is the proper way to send a notification from the Realm database when the date tobenotified is equal with NSDate() / the current date?
It's not as simple like that. Realm queries can neither match against a live-updating current date nor send notifications from the background.
You want to look into UILocalNotification and set it up with the tobenotified date as fireDate and schedule it locally. Note that you will require your users consent and have asked them initially by registering for local notification types so that you're permitted by the OS to schedule and present notifications. Also if the user can modify or delete a reminder, then you need to find a way to identify the notification via the the provided identifier and remove or re-schedule it accordingly.
presently i am using jenkins for continous integration i configured poll scm for 45 minutes.whenever the build fails it is sending failure notification to developers. Now i want in pom.xml to configure developers list. from here the jenkins should read and send failure notification who commit the code that person only should get failure notification.
What you need is a plugin called "email-ext"
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
Once installed, in the post-build actions, checkmark "Editable Email Notification"
Then, you have a choice of "triggers", for example "Fixed" or "Failure" or "Success", and checkmarks that let you select whom to send the email to for every trigger.
You have the option of sending to:
Recipient list - predefined list, either global or per trigger
Committers - those that made SVN changes for this checkout
Culprits - those that made SVN changes since last successful build
Requester - user that triggers the build
In your particular case, you would want a "Failure" trigger, and send email only to "Committers" and possibly "Culprits", and don't checkmark Recipient list.