Git Smart commit transition not working

[Divya Dias]

We have configured Git integration with our JIRA cloud instance (Classic projects). Through Smart commits, we are able to -

1. Add comments

2. Log time

3. See the commits linked on the JIRA Issue

However, we cant seem to get the transition working. Attached is a screenshot of my workflow. I have tried the following commands for a issue that was 'In Dev' - 

1. JR-1235 #done

2. JR-1235 #Done

3. JR-1235 #closed

4. JR-1235 #CLOSED

None of them transitioned the issue to closed status. 

I have cross checked that the email of user in git repo and jira matches exactly. Appreciate if there is anybody who can help me what i am missing here.

[Andy Heinzer]

Hi Divya,

Sorry to hear about this problem. I understand that you have Jira Cloud integrated with the GitHub for Jira app, however it sounds like the smart commits are not able to transition issues here.

I have this same integration setup within my own testing site, so I went through some steps to try to recreate this problem in my own site.  I found that I had to go to my GitHub configuration page in Jira Cloud to see the status of that integration.  You can reach this by going to [yourCloudSiteName].atlassian.net/plugins/servlet/ac/com.github.integration.production/github-post-install-page

In my case, I hadn't had a sync happen in months, maybe because I'm not using this as much I hadn't notice it appeared to be stuck.  But I was able to change the retry to Full and submit here, which changed my sync status to Complete instead.  That might be a factor here.  After I did this, I found that new commits I made were behaving correctly. 

If that isn't it, you might want to check the Configure button there to see if Jira is setup to use all the repos there, or only selected repositories.

But also for your particular use case here, options number 1 or 2 should work just fine here.  We need to use the transition name, not necessarily the status name you want to go to.  Many times these overlap or are the same (in the case of next-gen Jira projects there are no transition names yet, you actually do have to use the status name).   There are more details and notes on this feature in Process issues with smart commits: Workflow transitions.  It notes:

The committer's email address must match the email address of a single Jira Software user with the appropriate project permissions to transition issues.

It sounds like you already confirmed that part, but it might be worth checking to see if that exact same user has the ability to run that done transition to close that issue.

Try checking these things.  If you're still having problems, please let me know more here, such as, do you see the commit from the Jira issue?  If it's just the transition that isn't happening, I'd be interested to see what that commit looks like from within Jira when you click on the commits on that Jira issue.

Please let me know.

Andy

[Divya Dias]

Hi @Andy Heinzer

Thanks for the help in suggesting the above options. I have confirmed the following- 

1. A full sync was completed successfully.

2. User has required permissions to transition the issue to the desired status

3. Email of the user matches in github and Jira

4. Tried with transition names and status both, neither of these options worked.

Please note that i am able to get all other integration related capabilities like linking commits, creating PR from within Jira working. Here is a snapshot of a JIRA issue post the integration. I am only having trouble with the transitions. Do let me know if you have thoughts on what else i could be missing.

[Andy Heinzer]

Hi @Divya Dias 

Sorry that this has not been resolved yet. I'm not sure what could cause this behavior.  But I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-580734 Perhaps someone from our Cloud support team can take a closer look at your Cloud site, with your permission, in order to investigate this further.

Andy