Licensing: Is there a "freeze period" on user count after user deactivation?

[Konrad Trojak]

Hello Atlassian Community,

we are evaluating a potential business case, which assumes quite high rotation of active Jira users. Meaning that every month we would give access to let's say 50 or 100 new users, who after completing their assignments (month or 2) and moving to other teams/projects would be replaced (their Jira accounts would be disabled) by other people and so on.

Is there some kind of a "freeze period" in Jira licence terms, that would prevent this? Meaning - can I disable any number of users at any time and "replace" them with new users, and the users counted towards the licence will always only be the currently active ones?

Can you please advise how it looks like for Data Center and Cloud?

Many thanks!

Konrad

[Joe Pitt · Accepted solution]

Here are a couple tips that cause MANY people problems. 

Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.

. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.

The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.

Do not delete users

Users should be made inactive not deleted. JIRA uses a pointer to the user’s DB entry to display user information. If you delete a user when you open a JIRA issue the user worked on anywhere the user that would be displayed will cause a SQL error. Even if the user never logged on, if they were assigned a ticket the history of the ticket will get an error when you display it.

[Eric Fields]

Very good points...Thanks for sharing!

[Kat Warner · Accepted solution]

Check out the skill builders and tutorials here then follow the links on that page for more knowledge. :)

[Eric Fields]

Thanks so much Kat!

[Jonathon_McCutcheon]

Awesome, thank you for the links!