Hello,
I have a Jira Project where old members are still visibile on the roadmap and the backlog, even if they are deleted users. How can I take them out from these views?
As for the backlog, they have 0 issues assigned, while in the roadmap they have no un-completed issues assigned.
Thank you
Wow, does that mean Company, your customer, loses the ability to know who the person was that did the work?
That would be insane if true.
I am having same issue that old users are still showing up in surprised places and when I remove them, you show as REMOVED, when that is not true.
Atlassian is legally responsible for lying to people and telling them that users are removed when in fact, they are not.
You might want to discuss this with the Atlassian legal department, because words matter, and ACCESS REMOVED means ACCESS REMOVED.
Kelly Hill
I am starting to believe that much of the "cyber" attacks we hear about in the news is simply companies like Atlassian, Bitbucket and others having intentionally open and numerous backdoors that deleted and removed developers continue to have access to long after they have been "removed", "deleted" etc.
There are still numerous ways through invitations, links, completed tasks, etc, that they can still view and manipulate data in the Company's account.
This is my new belief from my own experiences this week. Do a search and see all the different ways, a developer must be "removed" and who knows if I have even found all the many ways they can still continue to access and manipulate information.
Kelly Hill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I will do more research and then do speaking engagements at SXSW on my findings...???? this could be interesting I guess... to let others know what I am discovering...
Alert the investor and CEO masses... they need to know if this is a question... and what about cyber insurance companies...
if you use companies with irresponsible practices then will we continue to be insured against "attacks"?
time will tell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Luca Galvani and welcome to the community. You'll want to perform an advanced search like this:
assignee in (inactiveUsers())
This will return all issues where the assignee is inactive. Then perform a bulk update to change the assignee.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So the only way to make them disappear is to reassign old issues? Even if completed?
Thank you for the answer :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. By design, Jira is not going to make the decision to manipulate history. Many organizations want to maintain that paper trail even if the employee is no longer with the company.
Another option is that you could set up automation to run on a schedule and label these issues as something like inactiveUser. Then update relevant filters to exclude those issues from results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.