You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a huge number of issues assigned to me or that are complete or no longer mine, and I need to change the assignee or the completion status. At the moment I'm making these changes one by one, but would like to know if there is a way to do this in batches. thanks!
Hi @Liz Ralph -- Welcome to the Atlassian Community!
Yes, and...to Mikael's answer:
What problem are you trying to solve by re-assigning completed issues? Why not just ignore updating those ones, only re-assigning the others?
What problem are you trying to solve by changing the completion status of a large number of issues? Is the work somehow "no longer completed"?
Thanks, and kind regards,
A great question and I'm sorry that I have taken 3 months to see your reply!
We had a change in personnel, where one person left and her role was split into 2 - so she had her name against hundreds of issues, and we want to transfer these issues to the 2 new team members.
I hope this helps!
I can understand the situation, and can see how re-assignment could cause unintended consequences...not just for reporting/history.
For example, let's say you are tracking down a decision/problem from an item completed in the past...and you wonder, "hey, that's assigned to Bill so let's talk to him..." Bill says, "I dunno...never heard of that..." which leads to probing the history and wondering why. Compare that to not re-assigning, where you see the item was previously assigned to "person-no-longer-on-the-team", and so the team swarms to figure the challenge out.
Perhaps instead of assignee, there is some role/area of responsibility which is common for the issues previously managed by a person. Using labels, components, custom fields, etc. to mark the issues could help find them later without changing the history.
Hi @Liz Ralph
welcome to the community!
Just to add to Mikael's answer, if you would prefer a more "interactive" editing experience, you could also try JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing and inline-editing all your issue fields. You can either inline-edit your values individually, or in bulk, using copy/paste - just like in Excel or Google Sheets.
This is how it looks in action:
(Note that JXL can do much more than that: From quick sorting and filtering, to inline issue creation, to issue hierarchies and groupings, aggregations and sum-ups. Disclaimer: I work on JXL :)
Hope this helps,