It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to bulk change Assignee or bulk change Reporter to another user?

How to bulk change Assignee or bulk change Reporter to another user?

I have a user that is no longer active within my projects and need to move all the tickets that were created by user and assigned to the user to another user. But i need to do this in bulk for the sheer number of tickes. Doing this ticket by ticket is not at all fisible.

How can i move reasigh this tickets to another user in buck?

I need the Assignee & Reporter changed, and i would really like not to delete the tickets but i would like to delete the user.

6 answers

1 accepted

Thank you.

How come i keep getting this on the options?


N/A Edit Issues
NOTE: You do not have permission to edit the selected 622 issues or at least one issue has a status that forbids editing.


Maybe some of the issues that you are going to edit are in closed status and it is not allowing the edit operation? Also check weather you have permission to do bulk changes.

To extend Jobin's answer. In case you still need to change the Assignee/Reporter of closed issues also, you could add a new transistion step in the workflow for your issuetypes that sets the value of "jira.issue.editable" to "true" while retaining the status as Closed itself. Do a bulk operation first for all Closed issues to clear this and then do a bulk operation for all the issues to change the Assignee/Reporter.

If this is one time activity, you could have an additional transistion to set back the "jira.issue.editable" back to "false".

Can you not add "and status != closed" to the search filter before running bulk edit? That way you'd only change non-closed issues and leave closed issues alone for historical reasons.

+1. As a JIRA global administrator, I'd like to be able to edit ANY field, regardless of the issue status.

Is there any way to NOT change the reporter or the assignee of closed issues.

We'd like to keep the names as they were, for histoical reasons, albeit move the tickets to a different queue.

Easiest way to do this is just using SQL in the database wink

I'm with you JMedway - I'd like to see a response from Atlassian on this. Seem's like something fairly common as people move in and out of a company.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Apr 09, 2019 in Portfolio for Jira

Portfolio for Jira 3.0 is here!

The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...

1,375 views 14 26
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you