Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

ScriptRunner Custom Listener

Does anyone have examples of a ScriptRunner custom listener on how to change the issuetype on the creation of the ticket?

In this case, it will be IF the ticket is created with a certain issuetype AND the description contains certain data.





1 answer

1 accepted

0 votes
Answer accepted

Changing issue type with any sort of automation is never a good idea except for the very rare case that the issue type has the same field configuration and workflow.

That's why the Move action is built like a wizard. There are many steps and decisions that have to be made along the way. That's difficult to predict in a script.

What I would suggest for your use case is a behaviour that raises an error if the description contains keywords that don't match the selected issue type.

Something like "based on this description, it appears that you want to raise a X issue type, but you have selected Y, please select Y or specify a description that's more in line with X"

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events