Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation: Change request type on creation

Ben Øye October 11, 2022

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?

Screenshot_5.png

2 answers

0 votes
Alex Koxaras -Relational-
Community Champion
October 11, 2022

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.

Ben Øye October 11, 2022

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 :)

0 votes
John Funk
Community Champion
October 11, 2022

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.

Ben Øye October 11, 2022

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.

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events