Why does Bamboo return Jira tickets used in a different build plan?

[Mark Erickson]

We have 3 build plans, Beta, Staging and Production.  Each build plan is linked to a branch in a VSTS repository.  We call the Bamboo API which returns the Jira tickets associated with the given build.  Our last production build included not only Jira tickets for Production, but included Staging tickets as well.  When you look at the production build details in Bamboo, you can see the associated Jira tickets split by build plan "Staging" and "Production".

The change sets were never merged into the production branch, so why does Bamboo think those changesets (and therefor the Jira tickets) are associated with production?

Thanks for any help!

[Gerhard Forster]

Hi Mark,

Thanks for your question in Community.

It seems that indeed VSTS, so Visual Studio Team Services can work together with Bamboo Server, at least I found this link providing a HowTo for your reference: VSTS and Atlassian Bamboo Integration.

Knowing that, let me get you some basic information about linking Jira issue keys to Bamboo build plans. It's nicely sketched in the following KB.

Linking Jira application issues to a build 

So basically you can either automatically link Jira issue keys to a Bamboo build plan and that per build comment, via build label or per commit message and thus directly from out of your source code repository / your commit and push process. Or you manually link a Jira issue key to a build plan per Bamboo UI, as illustrated in the above KB.

I don't know which of both methods you are following, or perhaps a mix of both. However, whatever Jira issue you link to a Bamboo build plan, you should see that Jira issue showing up for this build. Or in other words, any Jira issue not linked should not show up for this plan.

That said, I'd suggest to cross-check your Jira issue linkage in Bamboo on base of the above KB and verify that you did not adds some Jira issue key accidentially.

Hope this helps.

Thanks, Gerhard