When you initiate a build in Bamboo using the Release option in JIRA, the build has a custom variable of Jira.version (among others).
I would expect that when Bamboo creates the list of Jira Issues, it only lists the JIRA issues which are linked to the Jira Version by the 'FixVersion' field. After all, that is how a release is defined in jira; using the FixVersion field.
In addition, I would expect that the commits linked to a build are also only the commits linked to the jira issues with the FixVersion for the release i'm releasing.
However, the jira issues linked to a Bamboo build completely ignore the Jira Version parameter: it just looks at the latest commits since the previous build, and then looks at any jira issues mentioned in the comments of those recent commits.
This makes the whole Release option in JIRA a bit useless; you break the whole chain of version based releases.
Is there a way to make this work correctly in Bamboo?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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