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
One of our customers recently had a change in their email domain name? They were sent new invites to the new email address and reassigned the service desk customer role to their respective projects and have access to it via the Jira portal. Because they were reinvented with new emails and new accounts they lost visibility to their old tickets. I then went back an added the new accounts to the reporter field as well as the new organization with the new accounts to each of their 200 tickets. Is there a faster and more efficient way to do that?
Take a look at this link to use CSV to conduct a backend bulk change of all of your existing JSM project issues -
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Since the issue reporter will be different (regardless if it is just for one project or all projects), the CSV solution is the best way.
Otherwise you can use Advanced Search (via JQL) to select a subset of issues from one reporter, and then conduct a bulk change operation to change all of the specific set of issues to another specific reporter
Here is a link for you to take a look - https://support.atlassian.com/jira-service-management-cloud/docs/edit-multiple-issues-at-the-same-time/
Run a search to obtain all the issues reported by Bob Smith that you want to change to Mary Case....
Once the result set is obtained, then click on the "..." symbol (upper right of the screen), and then select 'Bulk change xxxx issue(s)" option. Afterward follow the instructions to complete the reporter update process.
Hope this helps.