-
Suggestion
-
Resolution: Unresolved
-
None
-
15
-
13
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Hi,
There are specific Issue Types that I would want a Service Desk issue created for as well as a Developer (Jira Software) issue created for.
I would like an automation rule, during creation, to copy information from the Service Desk input to a newly created Issue in a JIRA Software Project of my choosing (Developer) for a particular Service Desk Issue Type. Based on the Components selected, the Issue in JIRA Software might be created in a different project.
- relates to
-
- Closed
-
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
[JSDSERVER-3279] Automation rule to create new issue in another project with information from Service Desk Issue
Hi, has this needed requirement been implemented?
I need this function, does one need to be on premium to have these kind of option?
If this could be applied to a status change that would help, where a ticket status in service desk is changed (Task Accepted) and the ticket automatically moves to a project board backlog.
Current process:
- Clone JSM ticket
- Move ticket to new project
- Link ticket from Software project to JSM project
- Have rule to update JSM ticket when Software ticket gets updated
We do not want software developers in our ServiceDesk system and do not want Tier1 ServiceDesk staff inside Software projects/systems.
We're trying to find a way to automate this entire process. Looked at Scriptrunner with a Script Field to add a button onto JSM tickets for when ServiceDesk staff need to engage a Software user to complete the task but haven't found a way to make this work. Now looking at automation to trigger doing this based on workflow transition based on status.
Really annoying that there's ways to clone a ticket, move a ticket, link a ticket, but not do all three at once.
We have 6 teams of 5-10 using service desk and really need this functionality to orchestrate ticket flows that involve multiple teams.
We also need this functionality urgently. Please make sure that creating new issues is also possible through different instances via application links.
We have some interest in our organization for this feature out of the box. Looks like we might be able to hack it through a custom Jira Service Desk rule that triggers a webhook. But, that's not really ideal. This should work natively, if possible.