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; } } }

Jira software and Jira Service Management licensing

Venz

We have Jira software implemented on our end and would likely to add Jira Service Management. Some questions are below:

How would licensing affects both services, like the existing license in JS vs. license in JSM.

How would it look like? will it be separated or not?

Thank you.

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

The licencing is separate. You will have a licence for X developers (Jira Software users), and when you add Y Agents (people who will be working in your JSM projects), they are a distinct group on their own.

You may want to make your Agents into Developers as well, in which case, you'll need to allocate a space in both JSM and JS, and similarly, you might have developers who need Agent access too. But you can licence both systems totally separately, even when running in the same instance.

Mayur Jadhav_30osel

Hello @Venz ,

Welcome to the Atlassian Community!!

As Jira Service Management and Jira Software both different product, licensing is separate for both products.

For example you can have Jira Software -100 license/seats and for JSM - 50 license/seats, its up to your organisation need.

Note: In Jira Service management Agents consumes license ( Who actually work on ticket), you can Unlimited JSM customer and they don't need license ( Who submit the tickets).

I hope provided information is helpful.

Regards,
Mayur

Robert Wen_Cprime_

Hello @Venz ! Welcome to the Atlassian community!

A license to a Jira product grants you access to the product-specific features for that Jira product. For example, a Jira Software license allows you to see boards and set up versions and releases.

You still can do mostly things such as viewing issues, enter comments and attachments, and the like. A Service Desk agent (who consumes a JSM license) is the only one that can transition JSM issues.

Hope this helps.

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Mayur Jadhav_30osel

Hello @Venz ,

Welcome to the Atlassian Community!!

As Jira Service Management and Jira Software both different product, licensing is separate for both products.

For example you can have Jira Software -100 license/seats and for JSM - 50 license/seats, its up to your organisation need.

Note: In Jira Service management Agents consumes license ( Who actually work on ticket), you can Unlimited JSM customer and they don't need license ( Who submit the tickets).

I hope provided information is helpful.

Regards,
Mayur

Robert Wen_Cprime_

Hello @Venz ! Welcome to the Atlassian community!

A license to a Jira product grants you access to the product-specific features for that Jira product. For example, a Jira Software license allows you to see boards and set up versions and releases.

You still can do mostly things such as viewing issues, enter comments and attachments, and the like. A Service Desk agent (who consumes a JSM license) is the only one that can transition JSM issues.

Hope this helps.

Venz

Hi @Nic Brough -Adaptavist- , Thank you for answering my question. Just want to clarify, so let's say I have Developers (from JS) that might comment to tickets (in JSM), would they still need a separate license in JSM? to what extent we have to provide licenses to each products?

Venz

Thank you @Robert Wen_Cprime_ . Appreciate the information.

Venz

Hi @Mayur Jadhav , yes, it was helpful! Thank you

Nic Brough -Adaptavist-

No.

You can add any Jira user to any project. Your developers will only have limited actions on JSM issues available - they can be allowed to see, watch, and comment on JSM issues for example, without being given Agent rights. Agents can be given full access to Jira Software projects, but can't use the boards that issues appear on.

Venz

Great! Thank you for that information.

sean_0jwrrt

The organization I'm working with has account managers who can access, create and be assigned tasks in Jira. Separately, we have JSM projects with Agents and Customers. It looks like we can assign existing JS members (our account managers) as "Developers" in JSM so they can read and comment on JSM issues - but not be assigned them (the Agents are assigned the issues to work on). But what if we don't want to refer to the Account Managers as "Developers"? Is there another permission level or type we can use or apply to these existing JS members that isn't called "Developer", since they are not developers?

Aditya_z99zyk

Hi,

Same

Thanks!

Aditya K - Tirrah

Hi,

You can try this Marketplace plugin — it’s built to solve this exact issue. Faced the same problem for a long time, and this plugin does the job.

Marketplace link: https://marketplace.atlassian.com/apps/1237529/jsm-elevator?hosting=cloud&tab=overview

Thanks!

Jack Brickey

@Aditya K - Tirrah , please be sure to review the partner guidelines. Specifically....

Be transparent and authentic

When promoting an app or solution, disclose your company affiliation in the text of your post (e.g. “I work for the company that built this app”). State your company in your profile name, and request the Partner lozenge for your profile (instructions here).
We don’t use signatures or boilerplate language on the Atlassian community - do not use signatures or cut-and-paste content in every comment.
Don’t re-post or cross-post content. Tailor your responses to the users you’re talking to, and avoid coming across like a sales robot. Don’t reply to members with the same responses in every topic or question.

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