Imagine we have a build plan that is configured to trigger a deployment process. Thus, for each successful build a new release is automatically created and deployed. This is a common practice for development environments.
Sometimes we need to manually add an issue link to a build. (This could be a manually triggered build that nevertheless fixes some issue; or a developer might have simply forgotten to put an issue key into commit message). Since release is automatically created upon build completion, an issue link will be necessarily added after release comes to existence. Under this circumstances, it turns out that release has no knowledge of issues that have been manually added to original build. Finally, if we try to promote a newer build to some other environment, Bamboo will fail to compute correct difference in issues between the two builds.
Is this a bug? Or can we somehow update a release so that it reflects all the issues that have been manually added to the original build?
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