Hi guys! My intention (based on my prior experience with using the RapidBoard) is that when you remove an item from a sprint it goes into your backlog, however lately this isn't the case.
Steps to reproduce:
1. From the 'Active sprints' I can open an issue
2. From the issue panel I select the actions menu, and 'Remove from sprint'.
3. Warning modal shows; '(Issue id) will be moved from sprint (Sprint name) to sprint (Sprint name).'
Continuing down this path, it has chosen to move the item to one of my upcoming sprints (not started yet), instead of adding to the backlog list. This is causes a change to the sprint logs which is incorrect, and I then manually move it on my 'Backlog' page from the incorrect sprint to the backlogged unfiled items. Is this normal?
The funny thing is, I'm probably going about my intended task the wrong way. My end goal is to move a card from one sprint to another! Any suggestions would be much appreciated.
Hi Danelle,
When you're on the active sprints page, and you right click on a card to select 'remove from sprint' the expected behavior is that Jira Software will prompt you to confirm this move. Where it moves it depends on a whether or not that board has any future sprints planned at the time or not. If there are no future/unstarted sprints, then it will prompt you to move it to the backlog. If there are 1 or more future sprints, it will prompt you to move it to the very next future sprint instead.
This menu doesn't give you any options about where to place the issue at this time. Something that I think would really help you here if it did.
So I created a feature request for this in JSWCLOUD-17871. In my mind this just makes more sense, since when you close a sprint in Jira Software today, you get that kind of prompt for where to move incomplete issues anyways (backlog or future sprint), I think this would be more friendly and more consistent of a user interface when it comes to managing sprints.
In your case, since you want to move it to another sprint, and we don't know if that sprint is active or still unstarted, you can still remove this issue from the sprint, but in another way. Instead of using the right click menu of the card in the active sprint view, instead return to the backlog. From the backlog, you can either right-click and select one of the 'Sent to sprintname' options, OR you could left click and drag that issue directly to the sprint you want to move it into. In both cases you'll still see a prompt warning you about a scope change, but at least this way you can direct where you want that issue to go without having to move it twice.
I hope that helps.
Andy
I really appreciate your reply Andy. It's given me a work around, plus the forward sight into how my concern might progress. Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Andy Heinzer and @Danelle
It looks very interesting what you are talking about . But i have one question if you can help me .
Im using jira 6 (old version ) but the problem is when i try to move issue from Active sprint to other inactive sprint (future) , i dont find this option so i have always to remove issue from active sprint , so it comes back to the backlog , and then i can move my issue to another sprint . It looks weird , it's the normal behaviour ?
I would like to move issues between sprints directly , i do not like to go throught backlog every time .
Thank you
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Karim,
I believe that you are likely seeing an old limitation of that version of Jira Agile. There was a feature improvement in 6.3.4 detailed in JSWSERVER-7856. Before that version it wasn't possible to use the 'Remove from sprint' for issues in an active sprint. If you happen to be on a later 6 version, then it's also possible there are other more recent improvements to this feature in Jira 7 and higher that I think explain the differences you might seeing here.
Cheers,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Andy Heinzer thank you for your first reply , im using jira 6.02 , but i do not know if it's limitation or there are some thing to configure , i want to move issue from sprint active to other sprint without going through the backlog .
Thank you
regrads
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Karim,
You are seeing a limitation of this older version of Jira Agile. Sorry I don't believe there is anything you can configure in your version to give you that specific functionality. If you were to upgrade Jira Agile to 7.0 (where we rebranded it Jira Software) then I you should start to see more of these kinds of sprint management abilities on the active board itself.
If you do decide to try to upgrade Jira, I'd recommend first going to a 7.0.x version and then upgrade all plugins on that version first. Once you've done that and it appears to be working, you can then upgrade again to one of the latest versions, such as 8.5.x (Enterprise release) or the very latest 8.7.1. I'm a big fan of using the Upgrading Jira with a fallback method, it might take longer than a rapid upgrade, but I find it's much safer in terms of your data and rolling back the upgrade attempt is much easier in that method.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Danelle, from the issue detail view you can remove the current sprint from the sprint field. If you change the status also to 'to do' the issue will be placed on the backlog again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.