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

Change the issuetype with scriptrunner


I would like to change the issue type after receiving the ticket with scriptrunner.

The workflow is different from the entrance workflow but it is the same project.

The tickets are automatically created in the service desk by a mail handler. However, a different issuetype should be selected for one customer.

Do you have any ideas?

Many thanks for your help.



2 answers

2 accepted

0 votes
Answer accepted

Moving issues via scriptrunner or JAVA api is not trivial.

Think of all the steps you have to go through when you move an issue manually.
All those steps would have to be accounted for in a move script without the opportunities to prompt the users for many critical pieces of information. 

I haven't seen anyone implementing this successfully (and I haven't dared to try myself).

I think using a "Clone Issue And Link" or "Create Sub-task" post-function script as suggested in another answer will be your best bet. Both of those come with a "Condition" code block where you can examine the reporter's email address and decide whether or not to execute the function.

The condition script could be as simple as 


Just that single line will return either true (execute the function) or false (skip the function)

The rest of the function parameters are all form-driven, so no coding required.

0 votes
Answer accepted
Niranjan Rising Star Oct 07, 2020

Hi @Alexander Herrler - Why don't you consider creating sub-tasks instead of changing issue types of newly created issues You can create sub-tasks with the post-functions (script runner).

Thanks @Niranjan , thats a good idea.

But where in the script can I put an "IF" condition that the script only creates tickets as subtask when it comes from customer XY (E-Mail Adress)?

Do you know this?

Niranjan Rising Star Oct 07, 2020

Hi @Alexander Herrler ,

I am sure that the post-function of Sub-task creation can be done based on condition using Script runner. You may need to check how to identify issues created via emails. May be if the description has the email address of the sender, you need to validate the description field for the email address.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events