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

Assigning JSM ticket to developer who has access only to JS

Arevik Hakobyan

Dear Team,

Please advise how to assign JSM ticket to a user (developer) who does not take licensed seat in JSM?

Service desk agent has to assign the ticket to developer for follow up, who has access only to JS.

We thought maube we can create another issue (same type) in JS, and link JSM issue to it.

But then both issues has to be synced, since developer will only work for JS issue.

Please advise

Thanks

Accepted answers

Vilius Zigmantas_ckp1ha

Creating a separate issue in JS from JSM by agent would be the recommended way to go. Then agent could link to JS ticket and keep her JSM ticket open in the queue.

You could also figure out how to trigger JSM transition (to close linked issue) when JS ticket is closed using post-functions (though not sure this is possible without addons).

Julie d_Antin _Elements__bsgnak

Hi @Arevik Hakobyan

You probably will want to clone and move the issue to the right JS project. There are a couple ways you can do that: native Jira features, with Automation, with an app.

To get an overview of how each option works and the pros and cons of each, try this guide on cloning and moving in Jira.

Jack Brickey

You should use Create linked issue to create the JSW issue and use Automation to keep the JSM in sync with the linked JSW issue.

All comments

Vilius Zigmantas_ckp1ha

Creating a separate issue in JS from JSM by agent would be the recommended way to go. Then agent could link to JS ticket and keep her JSM ticket open in the queue.

You could also figure out how to trigger JSM transition (to close linked issue) when JS ticket is closed using post-functions (though not sure this is possible without addons).

Julie d_Antin _Elements__bsgnak

Hi @Arevik Hakobyan

You probably will want to clone and move the issue to the right JS project. There are a couple ways you can do that: native Jira features, with Automation, with an app.

To get an overview of how each option works and the pros and cons of each, try this guide on cloning and moving in Jira.

Jack Brickey

You should use Create linked issue to create the JSW issue and use Automation to keep the JSM in sync with the linked JSW issue.

Arevik Hakobyan

hi @Jack Brickey , and how can I create "linked issue" ?

Jack Brickey

In the detail issue view as shown below

Arevik Hakobyan

Thanks a lot!

Arevik Hakobyan

Thanks you very much!

Vilius Zigmantas_ckp1ha

Not sure whether cloning is the right way to go, depends on the internal policies (e.g. support agents might want to keep the request as a paper trail what customer asked for, then JS task would be a dependency linked to JSM and both tickets co-exists as separate: one to track customer request, another as an action item for customer request). Hope this makes sense.

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