Skip to main content
All CollectionsAutomationPipelinesGearset Pipeline management
Updating an Azure work item's status in pipelines
Updating an Azure work item's status in pipelines

How to link a Azure work item ticket to Gearset pipelines. Allowing for automatic updates.

Quinn Kuiper avatar
Written by Quinn Kuiper
Updated over a week ago

It's possible for Gearset to automatically update the Azure DevOps work item's status at each stage of a pipeline. This article describes how to configure that.

Note: Gearset currently supports linking Azure DevOps (ADO) work items, but this functionality is limited to Azure DevOps Cloud organisations. Support for work items in Azure DevOps Server (self-hosted instances) is not available.

How does it work?

Each PR can be associated with an Azure DevOps work item, as mentioned here. However, this additional functionality allows Gearset to update the ticket's status as it moves through each stage of the pipeline.

For example, a ticket status may need to be updated from "To do" to "In progress", once it has reached the Integration stage of the pipeline.

This supports both standard and custom workflow stages, so it can also be configured to update stages that you've added.

How to configure it?

1) When looking at your pipeline, access the settings by clicking the cog in the top right and then selecting "Edit pipeline details":

2) In the pop-up window, select the "Azure work items" tab to access the relevant settings:

3) From this page, select your pipeline environment, the stage you'd like the status updated at and the status you'd like it updated with.

The result?

This ticket currently has the "To do" status assigned to it. Within my pipeline, I've associated a PR to this ticket but not yet promoted it:

Once promoted into SIT, my pipeline automatically updates the status of that ticket to "Doing":

It's no longer need to do this manually as a post-promotion step.

Gearset will also comment on the ticket every time the PR is successfully promoted. The comments will be written under the name of the user who promoted the PR - as long as they have a linked Azure account with access to the ticket. If this is not the case, then the comment will be written as the pipeline owner.

Did this answer your question?