Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Not really used to complaining, I have been using JIRA for 8+ years and in general find it to be a great system for agile development teams... and I am probably screaming into the void here, but the "new" (ok it's been like this for a while) way to select multiple tickets in JIRA Backlog is BAD.
It's actually REALLY BAD.
So I've just been planning a sprint and wanted to move some tickets out of one sprint and into another. Should be simple, right? Select my tickets and use the wonderful "Move to" option.
NO!
I've selected the tickets and then - fortunately for me - remembered that JIRA is now retaining the selection of the last ticket I viewed.
So I have to search through all of my sprints and my backlog to find any tickets that have previously been selected, and de-select them one at a time so that I don't, for example, MOVE A BUNCH OF TICKETS OUT OF THE CURRENT SPRINT BY ACCIDENT (I've done this a few times and sometimes only realised weeks later when a planned piece of work did not get done in time).
Frankly this UX is rubbish and I can't believe there isn't a workaround.
Am I the only person suffering from this? Is there something I can do to make this work better for me?
Thanks, in anticipation and apols for the CAPS :)
I understand your frustration! Selecting multiple tickets in the backlog for bulk actions can definitely be cumbersome. While there isn't a perfect solution yet, here are a few options that might help:
While these aren't ideal replacements for the previous multi-select functionality, they might offer some relief. Hopefully, future updates from Jira will bring back a more intuitive way to select multiple tickets in the backlog.
In the meantime, feel free to share your experience and these workarounds with others in the forum who might be facing the same issue. You're definitely not alone!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.