Deactivating project or component leads in JIRA 6.3.1

[Ana Preda]

Hello,

Users who are project or component leads in JIRA cannot be deactivated from the UI unless we reassign other users as leads.

However, we can deactivate project, component leads from a plugin if we use the updateUser() method of com.atlassian.crowd.manager.directory.DirectoryManager:

https://docs.atlassian.com/crowd/2.7.1/com/atlassian/crowd/manager/directory/DirectoryManager.html

What's more, if we connect Confluence to JIRA for user management, then we can deactivate JIRA users from Confluence even if they are leads. Maybe this is based on the same Crowd API...

Questions:

Why is user deactivation restricted?

What is the proper way to deactivate project or component leads in JIRA? Is there any risk to break something else if we deactivate them through the use of Crowd API?

Thank you,

Ana

[crf · Accepted solution]

See my answer to the (nearly identical) question here.

Bypassing these checks is a really bad idea.  It is telling you very clearly that you need to assign different users to these roles.  Why would you ignore this and look for ways to trick it instead of doing what it tells you is the right thing to do?

[Ana Preda]

Because it takes time. We have ~100 leads that need to be reassigned and this would have helped us. I have simply noticed it is possible from Confluence, I didn't look for ways to trick it. That's why I was asking. Thanks!