agree here...but just imagin the following scenario:
an employee who left the company previously approved or commented on a certain request inside a ticket....now that you kinda remove this user as he left your company all your historic data will be gone once you delete the user. maybe 1 year after he left some issue or question appears where you need to find out who ever in the world approved this request....what you will find then is a wrong name...
i'd stick with the solution to simply deactivate exemployees accounts and leave the data as it is.
other than that where ppl have duplicate or multiple accounts an account merge mechanism would be pretty helpful. script runner plugin can proceed such a task but still this is not the optimal solution to rely on 3rd party tools like this. i'd like to see some improved account management anyway
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...staring into the background. Once the image pops out in 3D, you can look around the picture and enjoy. If you will see if you are a true illusion master! :) You did it? :) Wow! Awesome! As a bonus...
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