Smart Commits transition issues to an unexpected Status
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
A smart commit that's supposed to transition an issue to Status 1 appears to transition the issue to Status 2.
Example: for a unique Transition called Done, a smart commit with #done in its message should transition an issue to Status Done. However the issue is transitioned to Status To Do.
Diagnosis
Checking the issue's History, it turns out that:
At first the issue is transitioned correctly from In Progress to Done
However there's a Trigger that automatically transitions the issue from Done to To Do right after that
Checking the Workflow's XML file, there's a Trigger to Reopen the issue (from Done to To Do) when a Commit is Created:
1 2 3 4 5 6 7 8<step id="3" name="Done"> <meta name="jira.status.id">10001</meta> <actions> <action id="51" name="Reopen"> <meta name="jira.i18n.submit">jira.issuetracking.simple.workflow.action.reopen.name</meta> <meta name="jira.description"></meta> <meta name="jira.i18n.title">jira.issuetracking.simple.workflow.action.reopen.name</meta> <meta name="jira.autotransitions.triggerdefinitions">{"nextTriggerId":1,"triggerDefinitions":[{"id":0,"key":"com.atlassian.jira.plugins.jira-development-integration-plugin:commit-created-trigger","configuration":{},"triggerConfiguration":{}}]}</meta>ℹ️ this can be seen from the Workflow Editor in JIRA
Cause
While the smart commit transitions the issue correctly to Status 1, it accidentally activates the Commit Created trigger in that status which subsequently transitions the issue to Status 2.
Solution
Workaround
Modify the workflow to stop using the Trigger if not necessary
Avoid using Smart Commits where the destination status has a Commit Created trigger
Was this helpful?