Consider this scenario: Employee 1 has been managing a set of issues within JIRA. Employee 1 leaves and Employee 2 assumes all of the tasks and roles that Employee 1 performed, including all JIRA issues. Is there any way to link the JIRA user accounts of Employee 1 with the new account of Employee 2?
Employee 2 would just jump in and take over Employee 1's account. The idea has been put out there that the way to solve this is to make Employee 1 and Employee 2 part of a group that share access to historical data.
Anyone solve such a problem?
May be you should also re-look at the use-case of renaming the user. This can give a wrong impression that those issues which the old employee was working on, appears as if they are done by the new employee. If the concern is about permissions for issues, the best way will be to manage the project permissions for the project using project roles and define who belongs to those roles. By this way, who ever joins the new can be just added to the right project role, and he/she will have all the rights the earlier employee has, while keeping the updates from both of them distinct.
Currently this is not possible to achieve with JIRA. We already have a feature request opened for it, available here and I recommend to you vote on it. As an alternative solution, I believe that you can achieve it using a third party plugin, such as Script Runner. :)
I hope this information helps.
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
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!
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