I know that the idea with Jira versions is that when you have finished working on a ticket you set the fixVersion, and then you can release from Jira. However, in reality I find this does not work for us, mainly as we release fairly regularly; often we have small bugs within the system, or we have parts of the system that take a bit longer to finish off. As we are not on a hard and fast release schedule, this kind of releasing doesn't bother us too much.
However, we would like to know when something went out, as sometimes it is nice to see that that bug has now been fixed. Therefore is it possible that a bamboo deployment could push back to Jira the version number and the issues within that version. Rather than having to pre-empt which version we are going to release from Jira.
If you are working with jira and release board, you should be checking this board frequently, and prepare any hotfix in this way, jira is you ticket manager, when you commit the issue in bitcbucket (if you have) you can see in this board the build success o failed on bamboo.
But if you need push back to jira any infomation, you can achieve this with custom task bamboo and using the jira rest api.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot