We use the following workflows: * when a developer starts working on a ticket, the ticket's status is changed to `In Progress` * the developer will create a PR with the ticket number in the title, so that it will be linked to the ticket * when a PR is merged the following happens* a pipeline (we use Bitbucket) will deploy the app in the UAT environment. We use the `deployment` key in the pipeline so we can see exactly which PRs and tickets have been deployed * the ticket associated with the PR changes status to `Resolved` * when we want to deploy to Production we run the pipeline (this is a manual step). This pipeline also uses the `deployment` key, so we know which tickets have been deployed to production As you can see once a ticket has been deployed to Production it does not change status, and this is what I would like to achieve: change the status of all tickets that have been deployed to Production from `Resolved` to `Done`. Is it possible?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to change a ticket to Done after a deployment?

Giulio Troccoli-Allard_gj3x6y

We use the following workflows:

when a developer starts working on a ticket, the ticket's status is changed to `In Progress`
the developer will create a PR with the ticket number in the title, so that it will be linked to the ticket
when a PR is merged the following happens
- a pipeline (we use Bitbucket) will deploy the app in the UAT environment. We use the `deployment` key in the pipeline so we can see exactly which PRs and tickets have been deployed
- the ticket associated with the PR changes status to `Resolved`
when we want to deploy to Production we run the pipeline (this is a manual step). This pipeline also uses the `deployment` key, so we know which tickets have been deployed to production

As you can see once a ticket has been deployed to Production it does not change status, and this is what I would like to achieve: change the status of all tickets that have been deployed to Production from `Resolved` to `Done`.

Is it possible?

Accepted answers

Giulio Troccoli-Allard_gj3x6y

Although the above worked, it also failed. I don't really understand why, but the tickets where correctly transitioned and I also had a rule failure (for the same tickets).

What I did to fix it was to only transition tickets that were in the Resolved status Screenshot 2025-08-07 at 11.10.13.png

All comments

Howard Nedd

Hi @Giulio Troccoli-Allard ,

Yes, it is possible to automate the status (automation for jira) change of tickets from Resolved to Done after they have been deployed to Production.

You need to identify when a deployment to Production occurs. This can be done by setting up a webhook or a listener in your CI/CD pipeline that triggers an action after the production deployment is completed.

Then during the deployment process, you should have access to the list of PRs that were merged and their associated ticket numbers.

Ensure that this information is captured in a way that can be accessed after the deployment.

Does this help?

Regards

Howard

Giulio Troccoli-Allard_gj3x6y

Hi @Howard Nedd

It sounds like you're suggesting to do the work in the pipeline, using the REST API to change a ticket status perhaps?

I was looking more for something in Jira. I thought I would be able to use an automation, and I have tried (and still trying) but with no success. I can't figure out which trigger to use.

Howard Nedd

@Giulio Troccoli-Allard ,

Do you have an example of your automation? Like a screenshot?

I might be able to suggest something.

Regards

Howard

Giulio Troccoli-Allard_gj3x6y

I fell a bit stupid now, because I think I've got it (although I haven't tested it yet). Screenshot 2025-08-05 at 10.40.34.png

I don't know why I couldn't find that trigger before

Giulio Troccoli-Allard_gj3x6y

Although the above worked, it also failed. I don't really understand why, but the tickets where correctly transitioned and I also had a rule failure (for the same tickets).

What I did to fix it was to only transition tickets that were in the Resolved status Screenshot 2025-08-07 at 11.10.13.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

bitbucket-cloud

jira-cloud

bitbucket-pipelines