Previously issues removed from a sprint using right click could be put in a future active sprint. Now they go straight to the backlog. Is there a way to re-enable the behavior to put the issue in a future active sprint?
Could you let me know which version of Jira Software you are using? If you're using Jira Cloud just let me know, but if you're using Jira Server I am interested to know if there is a specific version that this might happen on.
In my testing, when in Jira 7.5.0, and when in the Active Sprint view of the board, I can still right click to remove an issue from the sprint. In my case it does explain that this issue will be placed into the next future planned sprint.
I am also curious to make sure that this board does currently have at least one future planned sprint. If the board does not have any future sprints planned, then you won't be able to send this issue to another sprint because none currently exist.
I hope this helps,
In my testing of my Jira Cloud instance, I found that if I'm looking at the Board - Active Sprints, then a right click here does not offer me options to move/remove this issue either.
But if I switch over to the Board -> Backlog view, then the right click on an issue in that sprint here, it does give me the option to move issues to a future planned sprint, or to send it to the top/bottom of the backlog. So that is still one way you could do this. But I understand this isn't exactly the same thing since you would have to switch views to do this.
This problem appears to be the same in my instance regardless if I'm using the new Jira interface or the previous interface. But considering the Server implementation seems to have this option on the active sprint view, it is curious that this appears to have been removed from Jira Cloud.
I did some more research into this behavior. This clearly was a feature of the Jira Cloud Software boards at some point in the past as displayed in this blog post about the new board features. But I was not able to tell exactly when this feature was changed/removed. I have not been able to find any clear documentation that explains this change. So in turn, I created a new bug in regards to this missing feature in https://jira.atlassian.com/browse/JSWCLOUD-16335
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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