It's possible for Gearset to automatically update the Jira status of a ticket, at each stage of a pipeline. This article is to describe how to configure that.
How does it work?
Each PR can be associated with a Jira ticket, as mentioned here. However, this additional functionality allows Gearset to update that 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's 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 "Jira" tab to access the relevant settings. Make sure the "Enable Jira Integration with this pipeline" box is ticked.
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.
Search Functionality in Pipelines
You can effortlessly search for and navigate to pull requests or environments. Simply click the search box or press Ctrl + K
to access it. You can search for pull requests by number, title, environment, or creator, and for environments by title, org, Git branch, or type. Selecting an item from the list will take you directly to it.
โ
โ
The result?
This ticket has currently got 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, my pipeline automatically updates the status of that ticket to "In progress":
It's no longer need to do this manually as a post-promotion step.
Gearset will also comment on the Jira 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 Jira account with access to the ticket. If this is not the case, then the comment will be written as the pipeline owner.