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?

[rsbeckerca · Accepted solution]

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.

[Trudy 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 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.

[Trudy Claspill]

I understand that you believe you have made no changes that would account for the functionality no longer working. Regardless of that, what have you done to try to debug this?

Have you reviewed the configuration for the integration of the tools to see that the integration settings are still present and correct?

https://support.atlassian.com/bitbucket-cloud/docs/connect-bitbucket-cloud-to-jira-software-cloud/

I understand that you say you have not modified the workflows. However, have you actually reviewed those workflows to confirm that the triggers are still in place?

I don't have a Bitbucket Cloud/Jira Cloud integration environment myself to explore this. I encourage you to review the documentation on how to set up the integration and review the actual settings in your environment to confirm they are correct. If the settings all appear correct, I would then encourage you to contact Atlassian Support directly.

https://support.atlassian.com/contact/#/

[rsbeckerca]

My plan does not allow me to open a support ticket on Jira, which is why I came here in the first place. Thanks for the help, but I am not getting anywhere.

[Trudy Claspill]

Oh, pardon me. I did not make note that you are on the Free plan.

Would it be possible for you to answer my questions about what you have done so far to confirm that your configuration and workflow settings are still correct? 

[rsbeckerca]

I don't know how to answer that as Atlassian did the configuration not me, so I cannot verify it is correct.

[Trudy Claspill]

A per this document

https://support.atlassian.com/bitbucket-cloud/docs/connect-bitbucket-cloud-to-jira-software-cloud/

...you should be able to see Bitbucket repositories in the "DVCS Accounts" page in Jira.

In Jira, if you click the gear icon near your avatar and select Products, in the new navigation pane that displays you should see a section for Integrations that lists "Application Links" and "DVCS Accounts". Can you share what each of these screens shows?

Can you follow this document to confirm that your Jira project(s) are linked to the expected Bitbucket repo(s)?

https://support.atlassian.com/bitbucket-cloud/docs/use-jira-software-projects-in-bitbucket/

[rsbeckerca]

I would have answered with information if the document came close to describing what I am seeing. There are no Atlassian Integration settings link. No Link Project link. Nothing, in my projects. This has changed recently, apparently. If you can forward this to support, something is wrong in the Cloud versions.

[Trudy Claspill]

I've added Bitbucket Cloud to my environment to try to assist you further.

Are you still able to access your Bitbucket Cloud workspace(s) and repo(s)?

Are you using a Free subscription for Bitbucket Cloud or a paid subscription?

Are you an admin for the Bitbucket instance or for that repo? When you're in the workspace in Bitbucket do you see the Settings option in the navigation pane?

If not, what do you see?

If you do see Settings within your Workspace, when you click on it you should get a new navigation pane/screen and the navigation pane should include.

If you don't see that (assuming you did have a Settings option) can you attach a screen image to show us what you do see?

On the Jira side, click on the gear icon near your avatar and select Products. You should get a new navigation pane/screen that shows options like this:

The navigation pane should include an Integrations section with "Application Links" and "DVCS accounts". If you click on "DVCS accounts", do you see any Bitbucket workspaces and repos? Can you attach an image of what you see?

[rsbeckerca]

I see. Under BitBucket/Project, I have the integrations set to point to the proper Jira workspace.

In Jira, under DVCS Accounts, the correct projects in BitBucket are listed.

[Trudy Claspill]

Good.

Next step, do your Pull Requests have Jira Issue Keys associated to them?

As per this document, you should be able to see associated Jira Issue Keys in the Jira issues panel located on the right-hand side of the selected Pull Request's screen.

Next, find a pull request that has not yet been merged that has Jira issues associated to it, as described above. Click the Merge button. Does it show you a list of the associated Jira issues after you click the Merge button? Then cancel out of merging the pull request.

If the Pull Request has Jira issues associated to it, but they are not listed when you click Merge, then per that same document there are either no transitions available for those issues, or the only transitions available require filling in additional fields. The next step in that case is to examine the field configuration and workflows on the Jira side.

[rsbeckerca]

There are no Jira issues listed. They are, however, highlighted in pull request and merge comments, but do not show up as an option to close. This is the behaviour that changed as of a few weeks ago. The Jira issue in question is in an In Progress state. The Sprint ends in a few days. There is a check box for closing the branch.

[rsbeckerca]

Ok, I found it. Atlassian changed to a new type of rule-based transition for issues. The previous rules were not preserved. I added the appropriate rules and now this works. This was pretty frustrating that there was no notice of this change.

[Trudy Claspill]

Can you please clarify where you found the information to solve the problem? Is there a product document or another community post that helped you figure this out?

It will help the community to learn from your experience.

It would also be helpful if you make a separate Answer on this Question that details the root issue (new type of rule-based transition) and where you found info about the solution. You can then mark your own Answer as Accepted to help other people searching on the same topic find your working solution.

[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.

[rsbeckerca]

The above should be the answer, but I could not post it.