Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Smart commit transitions work in next gen project but not classic?

Wade_Lahoda
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 6, 2020

So, I'm experimenting and trying to get Smart Commit Transitions working. In the Next Gen Project, it works just fine - I can transition to the Done state just with something like "NEXTGEN-5 #done #comment Finished the work".

But not for classic. If I do a commit message of "CLASSIC-3 #done #comment Finished the work" the comment will get picked up and display in Jira, but the transition will not fire. I've been reading on here and have checked some of the obvious culprits - capitalization of the state names, making sure the email I'm using in git matches my account name - but haven't figured it out yet.

 

1 answer

0 votes
PD Sheehan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 24, 2020

For a classic project, the smart commit command must map to the name of the transition between the current status and the next status. Not the target state name.

The transition name can be different based on the workflow. Generally, the transition name is the name of the button in the issue view.

Also, your workflow condition and validators must pass. So if you have a new required field when moving from one state to the other, the transition can't take place with a smart commit.

Suggest an answer

Log in or Sign up to answer