nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why use Jira Service Management?

Brendan Gray

I don't understand what Jira Service Management is for. Is it used explicitly for the purpose of customers having access to your projects so that they can see the progress?

If that is the case, then how can I set users who need to make changes and edits to our Jira projects and Confluence spaces, (I.e. be an administrator) but do not need access to Jira Service Management? Because having these people in Jira Service Management is taking us to a higher plan, but I still need them to be Administrators.

Accepted answers

Jack Brickey

JSM is a model where you have a support group or a potentially large number of customers. It is intended that customers don’t need full access to the application but rather just the ability to open issues and check the latest status via comments and a portal. Good examples of use cases include an internal IT support desk, external customer service support, HR support, facility support, etc.

JSM is not good for solutions where your team needs access to the application such that they can be assigned issues transition issues vote for issues etc. that is better suited for JSW or JWM applications.

finally regarding access to GSM in an environment where you may have JSW already as well as Confluence then you simply edit the users access by product. This is done under admin - user management and the details of the specified user. Anyone with JSM access is considered an agent and is licensed at a fee. Customers or JSM projects are not licensed.

All comments

Jack Brickey

Thiago Guedes_wlrgg4

Thanks for this, Jack! Helped me a lot.

Brendan Gray

Hi Jack, thanks for the reply. But I need some of my users to have admin rights, but to not have access to JSM so I don't go over my member limit. Does that make sense?

Jack Brickey

If a user is a Jira admin they have access to everything. That is the nature of being a Jira admin. Project admins are more limited and wont have access to all projects. If you were on a free project and you’re trying to control your user limit you absolutely should have only a single or at most two Jira admin’s. There’s really no reason for such a small deployment to require more than that.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management