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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira: Upon Bamboo build open issues are not moved to a selected release


Previously, upon Bamboo build, open issues can be automatically moved to a selected new version.
It does not work anymore. However if I just click "Release" issues are moved as expected.

1 answer

Hi @Tomasz Kosinski,

This does not sound like an out of the box configuration between the two servers.
In order to help us to understand what is causing this behavior, can you please share with us:

  • Are you using Jira Server or Cloud?
  • What is the Bamboo version you are running?
  • When did this configuration stop working?
  • Do you have any extra plugin for this?
  • If you are using REST API to change Jira issues from Bamboo, can you share them here?

That should be a good start to troubleshoot this.


I use Server edition

I believe that problem started to be visible when I updated:
Jira 8.2.0 -> 8.30
Bamboo 6.9.1 -> 6.9.2

Hi @Tomasz Kosinski

Can you share more details on how this is configured for you?
Are you using and extra plugin or REST API for this?

I do not use any 3rd parties. Its simple JRIA+BITBUCKET+BAMBOO. 
Bamboo builds are started form Releases pane in JIRA. 

Hi @Tomasz Kosinski

I'm writing to let you know I didn't forget you. I just needed extra time to set up the environment and test this. As soon I come into a conclusion I'll let you know.

I'm just registering here that I got in touch with you through email and as soon we have our meeting and a conclusion we can post our findings here.

we do have the very same problem - what was / is the solution?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events