VSTS Release Approval Emails - azure-devops

Using the 'Old Editor', there is a way to configure release environment to send emails to approvers via Release Definition > Triggers > Configure Environment as seen in this screen shot. (see also this answer)
Is there a way to do this using the 'New Editor'? Seems like the options for email and blocking the creating user from approving are missing from this workflow.

You can set Approval email notification in the page https://account.visualstudio.com/_notifications (by clicking profile -> Notification settings).
In the notications package, you can add a new subscription for An approval for a deployment is pending, and then specify the email address(es) and filter conditions.
with the integrated notification settings experience, we are moving
the control on notifications from the sender to the receiver. By
default, we'll always raise notification events whenever approvals are
pending and based on receiver's preferences around whether he wants to
be notified by email or not.
More details, you can refer:
Personalize what notifications you receive for releases
New Release Editor does not expose option to Send email to approver
Example:
In notification page, add a new subscription An approval for a deployment is pending, the detail settings as below:
Just add the email address(es) who need to receive this kind of email, for multiple email addresses, separate with comma (,).

Related

Azure Devops Build Complete Notifications aren't firing

Azure DevOps "Build Complete" Notifications aren't firing when there is auto-trigger fires the build because of a commit in the bitbucket git repo. The build and release complete with no issues but the email notifications don't go to all at all to the team members. The end goal trying to achieve is to send an email to the administrator and the user who has checked the code in the bitbucket repo.
By reference to this doc: Supported subscriptions, we can subscribe notification of Build completed, as below. Thus only members of artifact-demo Team can receive notification which meet the filter criteria.
From your snapshot, it is out-of-the-box (OOB) or default subscriptions, and will send notifications to all subscribers, by default. Thus members of Dev Team can receive notification.
Therefore, if you have a CI pipeline for bitbucket repository, and want to send an email to the administrator and the user (we call it contributor) who has checked the code in the bitbucket repo via Azure DevOps notification service, please make sure that the administrator and the contributor are members of Dev team, so they will get build completed notification. Otherwise, they need to subscribe such notification via Personal notifications or Team notifications
Update>>If you want to only send notifications to the administrator and contributor, you could choose "Custom email address" and then set up multiple subsciptions.
Or the administrator and contributor can subscribe this notification via Personal notifications.
BTW, if some users doesn't want to receive such notifications, they can manually unsubscribe it.
Update2>>Using custom email address will send email to specific user. And if you have 20 members, there might be too many subscriptions, you could consider to add these 20 members to a new group/team(NotificatoinTeam), and then just need to subscribe this notification for this group and choose "Members of NotificatoinTeam", so everything is done. If there is new member wants to get this notification, just adds them to this group/team. Also if some members don't want to get this notification, just remove them from this NotificatoinTeam group/team.
Update3>>You could use this predefined variable Build.RequestedForEmail to get the contributor's email. See: Build variables (DevOps Services) for more details.

Avoid being flooded by Azure Devops notifications

We have global notifications setup to send notification to work items assignees. But since there are many fields in these work items, users complain about receiving too many notifications.
We want to setup work item change notifications to be sent only when certain fields are updated, For eg. only on state and title change of a work item.
Is this possible in Azure Devops?
Yes, this is achievable in Azure devops. You only need to configure the filter criteria for the notification. See below example:
Navigate to the Organization Settings page-->Global notifications-->Statics tab-->Select the notification your team subscribed.
Then Edit the notification your team subscribed. Add the new clause in the filter criteria section to only send notification on the specific fields changes.
Check out document Manage notifications for a team, group, or organization for more information.

How can i get the hyperlink for "Approve", "Reject" work in Email using Apps Script

Problem: Seeking approval from manager upon each google form submission, the manager need to review the details and clicking approve or reject
BUT: how can i get the hyperlink for "approve", "reject" work
Desired solution: preferable Google Apps Scripts, when respondent click approve or submit, should save the response into google sheet and send second email to second layer approval
Tried: Able to extract detail from google form, but not able to perform approval and rejection button
A possible workflow is as following:
Use the form submit trigger - either for FormApp or, optionally, for SpreadsheetApp - if the responses are automatically stored in a destination sheet
Trigger onFormSubmit a notification email to be sent to the manager
Implement into the the notification email two links - one for approval, one for rejection
Create two WebApps - one that contains a script approving the form submission, copying the form response into a google sheet and sending emails to a second level approval; the second Web App contains a script that should be run in case of rejection (e.g. a notification email to the submitter about the rejection)
Use the Web App URLs as approval and rejection links in the notification mails to the manager
I hope those instructions are clear enough and helpful to you!

How to trigger an event in VSTS when there is a state change

Am looking to create a trigger (A json payload to a server) when an User Story is changed to closed/resolved state.
I am following this documentation
How to trigger an event in VSTS when there is a state change
First, Azure Devops has capabilities to set up email notifications for the work Item. Check this the document Manage your notifications for some more details.
For you requirement, you could add a new subscription with following settings:
Then, if any User Story is changed to closed/resolved state, you will receive a e-mail about it.
Besides, if the trigger event is more than just a e-mail notification, like build. You could configure a service hook to send request to build related builds:
Check this thread for the details.
Hope this helps.

Prevent Dynamic CRM Workflow from sending an email to a Disabled User

I am using Microsoft Dynamic CRM Online and have a workflow issue. When the status of a case is modified, there is a workflow that kicks off to send members of the case team an e-mail. The problem is, it is sending the message to members of the team that have been recently disabled.
Example: User Jack Bauer is added to Case FOX24. One month later, Jack's account is marked as disabled. The following week, the status of the case is updated and a workflow is triggered to send team members an e-mail.
Is there a way inside a workflow to prevent the email from being sent if the user is disabled?
So far, I haven't found anyway to stop the email.
I solved my problem by creating a child workflow to remove any disabled users from the case specific attributes before the email is sent. The new process contains the nine checks for disabled users as well as an Update Record action for each check to {clear} the value of the associated attribute. It is marked as "Run on demand" so users can clean the Case record anytime they desire.
The child workflow will be called once per email in the parent workflow because they are sent using different timeout periods. Even if a user is disabled in the week or so between the first and second message, they shouldn't receive the messages.
Add a condition into the workflow which checks the status of the record in the 'To' field of the email.