Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How Issues (JIRA tickets) are added to Release of Deployment Plan in Bamboo?

Kamil Ciecierski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 19, 2019

I would like to understand how the list of the Issues (JIRA tickets) related to given Release of Bamboo deployment plan is created. I mean the list visible in tab presented below when Release details are displayed:


We observed this behavior:

We have two branches: A and B and JIRA ticket TIC-1234.

The changes for ticket TIC-1234 were developed on branch feature/TIC-1234 and then this branch was merged with PR into branch A. The ticket TIC-1234 has Fix Version set to R-201908

After that, we created Release-A-R-201908 from branch A. When we check Issues tab in this Release details, it properly contains JIRA ticket TIC-1234 on the Issues list.

Later on, we have merged branch A into branch B and created Release-B-R-201908 from branch B. It looks that list of JIRA tickets in Issues tab of release created from branch B does not contain TIC-1234. At the same time, it is impossible to compare Release-A-R-201908 with Release-B-R-201908. using dropdown from Issues tab, as these are releases from different branches.


Base on that we would like to understand if:

* the list of JIRA tickets in Issues tab of given release excludes tickets which commits were part of another release, even if that release was created from different branch?

* is there any way to include TIC-1234 into Release-B-R-201908 and make it displayed in Issues tab of this release?

* what are recommendations deal with such scenarios (when we do releases from different branches) to make sure we will get the list of issues to release that contain issues of releases created from other branches?



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events