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; } } }

What happened to automatic marking of Done on Jira tickets?

rsbeckerca

Since moving to Jira, we had a good process where referenced Jira tickets in our git commits would move to a Done state. The Pull Request would prompt on the Merge for up to three tickets to be moved to Done. This stopped working about three weeks ago. There is now no provision for this process. All moves to Done have to happen manually. This is not a good user experience. What is the justification for this change and can we have it back?

Accepted answers

rsbeckerca

I sent to the Jira project administration under Automation and found that there were no automation items associated with the project. Once that was apparent, it was clear that no migration to the new automation engine was done by Atlassian. After that, it was simply matter of turning on the various items I wanted, particularly what happens when a pull request is merged, to move referenced issues to done. I would still prefer to be prompted for whether the issue is truly done, but I am not going to argue that point.

Thank you for your help.

All comments

Trudy P Claspill

Hello @rsbeckerca

Are you the person who set up the configuration so that process would be executed?

This is not a process that happens by default. Somebody has to go through the steps to integrate your development tools with Jira, and set up the workflows to include Triggers in the transitions so that the change of status can happen.

Is the integration configuration for your development tools and Jira still valid?

Doe the workflow transition(s) to the "done" statuses still include the appropriate triggers? Have you added new "done" statuses to the workflows?

rsbeckerca

I did the original transition to Jira when it was made available on the cloud version. The default workflows handled the transitions just fine. The configuration has not been touched in a year, but stopped transitioning issues about 2 weeks ago with no action on our end.

Trudy P Claspill

Have you double checked that the integration configuration for your development tools and Jira still valid? With what specific development tool did you integrate? Have there been any changes to that tool?

Have you double checked that the workflow transition(s) to the "done" statuses still include the appropriate triggers?

rsbeckerca

The only integration is with BitBucket Cloud, and Atlassian set that up initially. We did not touch it. If the change in the tool broke the workflow, then there is a bug that Atlassian introduced. We have not modified Atlassian's workflows.

rsbeckerca

Thank you for your help.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud