The client i have has a very high JSM license usage any wants to know why. They're trying to understand what kind of overlap exists between the licenses to get a better understanding of why the JSM licenses seem so high, why it got so high, and what are good discussion points to start thinking of how to trim it down and keep it under control. Any ideas on how i can put this info together for the client? I'm lost.
I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.
A user counts towards your licence count when their account is given permission to act in a certain role.
In most cases, it's as simple as "can log in and use Jira", for Jira Work Management, and for Jira Software, they also have access to the Software functions.
For Jira service management, the licences are for "Agents" - that is anyone who is an Agent role in at least one JSM project.
The usual reason for licence usage going up when it should not is people leaving their roles, but no-one removes them from their roles in Jira, so their accounts still count against the licence. And, of course, they are usually replaced with someone else, who then consumes another licence.
You need to talk your admins first - are they making leaver's accounts inactive? (Not delete, it is a bad idea, it causes problems. But an inactive account cannot log in, won't be offered as selectable assignees or in other user fields and, most importantly, do not count towards the licence count, even if they are not removed from the roles.
Then talk to your JSM projects owners. Why are they adding more agents to their projects? Are they removing Agents when they no longer need them?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.