I have Service Desk and JIRA Cloud setup.
Within Service Desk, I have a large number of request types (this is linked to Zendesk and other systems for various customer support folks.)
I want to use JIRA Automation to automatically assign all tickets that come into the queues with a specific request type to the same assignee that's found on a ticket in another JIRA project.
* TICKET-123 has an assignee of Mark
* SERVICEDESK-1 request was made
* Automation should run and copy the assignee from TICKET-123 to SERVICEDESK-1
I've tried to use the following and it is not working. I am sure there is some update to the JQL that I could make... or maybe it's just not possible to reference an issue in JIRA from Service Desk?
When: Issue Created
And: Request Type = ABC
Then: Assign the issue to:
Hi @Mikeb ,
Question, how is the link established between the Service Desk issue and the Ticket issue?
For a client of mine I have a request type with an issue picker field on it. And with a Behavior (scriptrunner) I take over various fields (fields also included by request type (not mutable)) from the issue chosen in the issue-picker field.
I am not sure I get your meaning?
But firstly, our organization does not have Scriptrunner.
As far as linking the JIRA ticket and the Service Desk (SD) ticket, the only connection is the JQL within Automation. My understanding is that despite Service Desk being a separate "app", it's still within Atlassian's ecosystem, thus JQL can and will return any data within SD, JIRA, or Confluence.
I need this to be as simple as possible and without any paid add-ons like Scriptrunner.
The assignee of the other issue does change every two weeks, yes.
The root of the problem we're trying to solve is that the Service Desk tickets need to be auto-assigned to an on-call Engineer. However, the round-robin, etc options in JIRA are not what we want as this is a "static" value (user) that changes every few weeks on a constantly updated schedule determined at bi-weekly sprint planning sessions.
So, we've set up a ticket in a project (TICKET-123) that will not get closed. We update the assignee of TICKET-123 each sprint planning session. The desire is that we have Service Desk tickets with a specific Request Type assigned to the assignee of TICKET-123 automatically.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events