-
Suggestion
-
Resolution: Unresolved
-
866
-
370
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
Product Manager, JIRA Platform
Original request description:
There are a number of situations where you want to delete a user - but transfer all of their reported/assigned issues to someone else.
We have a large number of duplicate users - and we also have had some people leave - and we want to delete them.
"Merge Users" is the best description I can think of.
- blocks
-
JRASERVER-70689 Fix "gathering interest" issues assigned to inactive users
- Gathering Interest
-
ID-240 Ability to merge Atlassian accounts to a single account with secondary emails
- Future Consideration
- duplicates
-
ID-240 Ability to merge Atlassian accounts to a single account with secondary emails
- Future Consideration
- is duplicated by
-
JRACLOUD-35458 Merge accounts and change usernames.
- Closed
- is related to
-
JRACLOUD-964 Delete user UI enhancement
- Closed
-
JRACLOUD-2220 Deactivate user
- Closed
-
JRASERVER-3132 Provide ability to transfer reported/assigned issues to another user when deleting users
- Not Being Considered
-
MOVE-119788 Loading...
- relates to
-
JRACLOUD-1549 Ability to rename a user
- Closed
-
JRACLOUD-3151 Assign all open issues to another user
- Closed
- aligns to
-
ENT-1477 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...