Email related items when a pipeline fails in Azure DevOps

Trigger — Pipeline run state changed

Fires when a pipeline run starts, is canceling, or finishes. YAML and classic builds are both included. A finished run starts the automation once. This template starts when the run is Completed and the result is Failed, for any pipeline in the project.

Configured in this template

• Pipelines: any pipeline in this project
• Run state: Completed
• Result: Failed

You can customize

• Limit Pipelines to specific definitions if only some runs should send this email.
• Change the result if a canceled run should send mail as well.

Get — Get pipeline work items

Loads the work items shown as Related on the run. If that list is empty, this step reads the work items linked to the run’s changes. It uses Read pipelines and work item access, not the code repository. If those changes are not ready yet, it waits until the run finishes. Work items in another project are left out. The email lists these items.

You can customize

• The email body lists the items this Get returns. Work items in another project are not included.

Action — Send customized email

Sends one HTML email through the platform mailer. The subject names the failed pipeline and run id. The body links to the run and lists the work items from Get with {#Items}.

Configured in this template

• To: (empty — add recipients)
• From: notifications@documentero.com
• Subject: `Pipeline failed: {trigger.Pipeline.Name} #{trigger.Pipeline.RunId}`
• Body (HTML): `<p><a href="{trigger.Pipeline.Url}">{trigger.Pipeline.Name} #{trigger.Pipeline.RunId}</a> failed.</p><p>Linked work items:</p><ul>{#Items}<li><a href="{Url}">#{Id} {Title}</a></li>{/Items}</ul>`

You can customize

• Add recipients in To. The builder blocks enable until To is set.
• Edit the subject and HTML body. Keep {#Items} if the email should list the related work items.