Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Handling inactive users from a legacy system and license limits of Jira Software DC

Hello there!

We are evaluating Jira Software Data Center as a candidate for a corporate task management system.

One of the requirements is to import history from our current system. The system has been used for many years. Naturally lots of users mentioned as reporters, assignees, commenters etc in the legacy data are no longer working in the company. But it is critical to preserve the information after moving to Jira.

Could you please help us with information on following questions?

1. If those inactive users are imported to the system would it inhibit usability of the system in any way?

I don't have any examples, but perhaps someone experienced some side-effects.

2. How to make sure that those users are not counted as licensed users? Would it be sufficient to strip them from any User groups?

We are going to use Security Levels extensively with permissions based on Issue fields (native like Reporter, Assignee, and custom fields as well). Is it possible for the permission granted to the inactive user mentioned as, for example, Reporter to make the user a licensed one?


2 answers

1 accepted

1 vote
Answer accepted

Hi @Alex Trebek , it is simple and complex at once :). Users which are able to log in are calculated towards the licenced users (you can read more:

Complex part is that Jira can contain more applications (Jira Core, Jira Software, Jira Service Management).

But basically -> removal of groups is sufficient to not to have user counted as licensed user.

ad Security levels) You can't set inactive user as reporter because of this issue:

hI @Alex Trebek

for the Security Levels topic... if the user is part of the Security Level and the user is Inactive, usage of Security level will not affect this user... this user is still not able to log in... is it what you asked? :)

Hello @Martin Bayer _MoroSystems_ s_r_o__ !

Yes, I was concerned precisely with this matter.

Thanks a lot for the clarification!

Hi @Martin Bayer _MoroSystems_ s_r_o__ !

Thank you for the prompt response.

Good to hear that our assumptions are correct. We are really close to the user-tier upper bound, that's why it is important that no more users are counted as licensed than necessary.


But the question about Security Levels is still open.

Inactive users can be set by importing/updating issues through CSV/JSON import. Exactly the way the legacy data will be imported.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

109 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you