Having read through the documentation to integrate Jira and GitHub, I've also ensured my git email is configured to my Jira email.
On some test issues, I am able to see my commits and comments pulled in accordingly, but attempts to use smart commit syntax like `#close` or `#resolves` refuse to change the status of the item.
Does it have anything to do with the lack of custom workflows in next-gen projects?
Hi Alan,
Sorry to hear of this problem. If I understand correctly, you're using the Github for Jira integration with Jira Cloud, but you are unable to transition an issue in a next-gen project when using smart commits.
I don't think that this JSWCLOUD issue you linked is the direct problem here. That specifically is dealing with the ability to edit workflows in next-gen projects. It's true that next-gen does not have that ability today, and that requests such as JSWCLOUD-17721 seek to have clear workflow triggers in place for next-gen.
That said, I tested this out in my own next-gen project integrated with Github as well. I found that I was able to make these issues transition using smart commits. One of the differences with next-gen when it comes to smart commits, is that in next-gen we have to use the status name. Whereas in classic, you have to use the name of the transition itself. Many times these can be the same in classic projects, but not always.
You mentioned being able to see the commit message in Jira. What does it look like for you? In my example, I had the message as such:
NGKN-5 #Done #comment now it should be done
This both transitioned that issue to the Done status and left a comment. This was an issue in a next-gen project. What is the name of the status you want this issue to be in here? In my example, the status is Done.
Please let me know.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.