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 do Stakeholders in JSM have to be full licence holders?

Jason Selby

In my organisation when a change is raised there are certain individuals " Stakeholders " (Definition - a person with an interest or concern in something, especially a business.) Who need to be informed and have visibility. I was going to automate this to be a stakeholder or responder but have just found out that this needs to be a full licence holder, is there another way or an explanation why ?

Accepted answers

Hana Kučerová

Hi @Jason Selby ,

in general they need to have Jira product licence to be able to log in to Jira. If it is enough for them to only view the issues and get notifications, they don’t need specifically Service Management licence, they can have Work Management or Software, which are cheaper.

All comments

Hana Kučerová

Hi @Jason Selby ,

Jason Selby

These users are customers and Altassian Access users. They dont use any of the software aforementioned, why do they need a licence when they just need visibility? They log tickets but dont have any other interaction, surely there is another way to make them aware?

Hana Kučerová

If they are customers, you can add them as Request Participants to these issues and they will be able to view the issue via portal and receive notifications about changes.

Jason Selby

Yeah I was aware of the request participants, i just thought that there would be a better solution for "Informed " users. Thanks for taking the time to respond

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