Actions in Bitbucket failed to trigger JIRA Issue Status Transition

[Wenjing Xu]

One of our classic JIRA project workflow stop working as expected. The problems are on the automated issue transitions:

1. Related PR already merged in Bitbucket, but the JIRA issue is still in TODO / IN PROGRESS / IN REVIEW status.
2. Related PR created in Bitbucket, but the JIRA issue won't automatically transit to IN REVIEW from TODO / IN PROGRESS as designed.
3. Related Commit Created in Bitbucket, but the JIRA issue won't automatically transit to IN PROGRESS as designed.

The workflow has been working fine for months. I have went through the trouble shooting documentation https://confluence.atlassian.com/adminjiracloud/troubleshooting-workflow-triggers-953138869.html and seems none of the possible cause met.

One thing might cause the mass is that I added several JIRA Automation rules weeks ago. The automation rules have some sort of duplication with the JIRA workflow. But after I disable the Automation Rules, the issue status still not corrected.

Any ideas how to solve this problem? Thanks in advance!

[Petter Gonçalves]

Hello @Wenjing Xu

Thank you for reaching out.

Per your description, it seems that the triggers are not properly working only for a single workflow on your site, is that correct? can you confirm if there are any other projects/workflows where the triggers are properly working?

The documentation you are following is the correct one to properly troubleshoot your issue, so please provide us with the information below so we can better troubleshoot it:

1. When running the trigger diagnostics as mentioned in the first step of the documentation, what results did you got for the 'Trigger sources' and  'Transition failures' sections?
2. Check if there are any conditions or validators in your workflow transitions that can be blocking it, as permissions conditions or field required validators.
3. Did any changes were added to the workflow since the last time the trigger worked? You can check the last time the workflow was edited by navigating to Jira settings > issues > Workflows > Click to view your project workflow:
   
   P.S: You must be a Jira administrator to check this information.
4. Logged as a Jira Administrator, navigate to the following link (Updating "yourdomain" with your current site domain) and check if your Bitbucket repositories are properly linked to your Jira site:

   https://yourdomain.atlassian.net/secure/admin/ConfigureDvcsOrganizations!default.jspa

5. Under the Code tab in your project view, confirm if your repositories are properly displaying under the Repositories section:
    

Let us know if you have any questions.

[Wenjing Xu]

Hi Petter,

Thanks for the instruction! Below are the findings, please advise. 

1. The "Trigger Sources" showing 2 connected repo working fine, and an unknown repo is not connected. "Transition Failures" was not found.

2. Yes there are field validators, but even the validators are satisfied, the issue still not transiting.

3. The last edit of the workflow was April. And the transition problem happened recently.

4. "Your GitHub.com integration using the DVCS Connector has been disabled", is this possible to be a problem?

The Bitbucket connection was fine, and the development info are showing correctly on the JIRA issues, which indicate good connection between Bitbucket and JIRA.

5. Wasn't able to find Code. 

Thanks

Wenjing