I have been tasked with finding best practice on changing Request Type and Issuetype on creation.
We have 2 Request types: Support and Aftermarket, they do not share the same workflow.
Default entry is Support / Consultant , case can be MOVED to Aftermarket / Various states,
Since they dont share the same workflow simply using Edit issue field will not work.
My suggestion to the automation added as a screenshot. The only "downside" is that each case of this automation will spend 2x number series, first creation will be deleted and correctly assigned case will create a new ticket number.
Any feedback to the selected solution, and if any a way to accomplish this without creating new issue for each occurance?
Hi @Ben Øye and welcome to the community,
Do you have any other app installed on your instance like Scriptrunner or JMWE? I've implemented such changes via these apps.
Hello @Alex Koxaras -Relational-
Currently not using either of these apps, and im guessing that if it stands between my suggested automation and spending 3-4000$ pr. year for a single automation it will be my automation for now :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ben - Welcome to the Atlassian Community!
Yes, unfortunately, you have the best way to solve this because you cannot do a "move" using Automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @John Funk
That was my assesment also after using my google-fu capabilities for the last 4 hours or so, atleast without resorting to other apps/plugins to JIRA for this one single task.
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.