Why can't anybody else then servicedesk operators edit incidents

We're running JIRA servicedesk because we want to monitor SLA's on our incidents. But we want to be able to assign incidents to people outside of the IT Operations, to product owners and developers in scrum teams. We can't all make them operator, that would be too expensive. So now our servicedesk has to clone all the issues to seperate projects which is very inefficient. I don't understand why Atlassian has chosen for this impractical solution.

2 answers

0 vote
Steven Behnke Community Champion Aug 01, 2016

The Create and Link operation allows you to create and link problems to incidents. The Problem could for instance be created in a JIRA Core or JIRA Software project. Atlassian has added a usable event to the Automation engine that allows you to action an issue if a 'linked' issue is transitioned.

The desired workflow in this instance would be to Create and Link an issue. The receiving party can do whatever they want, how ever they want. Then during a transition, you can do the following – 

  • Post an Internal comment
  • Post an External comment
  • Transition the issue

The default rule that comes out of the box includes a filter to only include incidents linked with causes/is caused by link type, and to only perform the action when the other issue is resolved.

Yes but we'd still have to create and link an issue by hand for every incident that is created, which is wildly impractical. All i want is to have the opportunity to have a project "incidents" that can be assigned to anyone and to measure SLA's on it. At this moment the only advantage i see in JIRA servicedesk is the SLA timer, and maybe the customer portal but it's not that hard for our business to create incidents in the regular JIRA way anyway.

I'm in same situation (using cloud), I want my developers to see only issues assigned to them (which doesn't seem possible) even if they ARE service desk agents).

 

I tried the linked issue and I'm OK with it because we don't want all internal developer comments and stuff in service desk, but I DO want to know it' status in the software project, who it's currently assigned to and most importantly, when they mark it DONE, a notification or status change in ServiceDesk.

I'm pretty new to JIRA, so still trying to figure things out

Vote on this: https://jira.atlassian.com/browse/JSDSERVER-931

It's a limitation in the licensing scheme. Only full fledged agents can do anything useful with tickets which is a bit bizarre.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,211 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot