We are setting up Jira Service Desk for our team and I'm not understanding what I need to do (as the admin) to enable non-agent Jira Software users (developers) to be able to transition Service Desk issues.
TIA
We have implemented Automations for Service Desk projects that Developers can access that can transition the issues. A bit clumsy, but this is a workaround.
Hello @Janene Pappas ,
I would very appreciate it if you could share the automation screenshots so I can implement it for my project too.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a very late reply, but can't you just edit the permission scheme for the Service Desk project to allow the Developer role to transition issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, the permissions for this are restricted to agents.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As far as I know you cannot.
Only agents can transition JSD issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow. I'm a bit amazed. Agents create ticket, developers work on fixes and need to give updates but don't need agent licenses to do that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But developers are used to work on JSW projects... anyway they can create internal comments to warn support team that a new bugfix has been released.
Also, you can use issue link features to trace both issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, I understand the current state of things but that is not what I was expecting. Forcing our agents to do all of the transitioning isn't optimal. I'm looking into automatically transitioning when linked issues have changes but workflows are tricky to set up correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.