I currently have a repository which contains the JIRA issue ID so when I first run the plan, the job auto links it to JIRA successfully. However, it seems that any subsequent jobs do not recognize the commit. I suspect this is because it is not considered as a 'new' commit anymore.
I do not want to have to link the plan/job to JIRA manually. Is there way to get around this in the event the plan is run manually?
Thank you for your question.
In case you are committing something to a repository (i.e.: Stash, Bitbucket) you can add JIRA's issue key to the commit so when Bamboo runs the build, the same will be automatically linked with the JIRA's issue(s) you have provided in the commit.
Please, refer to Processing JIRA issues with commit messages documentation for further information.
Now, if you are running your build manually, Bamboo does not know to which issue (in JIRA) the build should be linked to. In this case, I am afraid you will have to add it manually.
If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.
Thank you for your understanding.
Rafael P. Sperafico
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs