It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Using Service Desk Automation + Create on Transition

I'm trying to utilize the built-in Service Desk Automation tool in conjunction with the Create on Transition plug-in.

I'd like to utilize the Service Desk Automation tool for a simple If/Then.

Trigger: Issue Created

If field = y

Then update Issue field, Environment = x.

That works fine.

Then I want to set a custom field on a new issue utilizing Create on Transition.  Custom Field will equal the Environment field from the original issue (x).

I have Create on Transition working successfully, however it is not setting this custom field.  (It is setting other custom fields successfully.)

If I instead use a Post Function to set the value of Environment, then it works great (but then I can't utilize If/Then conditions.)

So I'm suspecting that this is an order of operations problem.  The SD Automation is not running before the Create Issue Post Function.  

Does anyone have any ideas about where SD Automation fits within the Post Function operations?

3 answers

In your list of Post Functions, you have, normally a list of events / actions that occur (just a stock list):

  • Creates the Issue Originally
  • Re-index an issue to keep indexes in sync with the database.
  • Fire a Issue Created event
  • <<other Post functions / Custom steps>>

I assume your automation picks up as soon as the "Creates the Issue Originally" event occurs. 

You may want to look into JIRA Misc Workflow Extensions instead, as you can create a small groovy script that follow the if/then condition and auto copy the information between fields. 

0 votes

If you want to go a step further than simply create an issue on a certain condition, but also keep it synchronized with the original request afterwards, you could also choose an issue synchronization app from the marketplace.

Since I'm working for K15t, I'd obviously recommend Backbone Issue Sync, but that's a choice you have to make.

If you're interested in a discussion of your use case or demo, let us know at

Thanks for the replies.  I will check those out.

Just to chime in on the suggestion from Matthias to use Backbone for synchronization.

Exalate provides on top of a robust synchronisation engine a scripting engine which provides the flexibility to implement any use case you might have in mind


Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Apr 08, 2019 in Jira Service Desk

What's new in Jira Service Desk Server: A stylish new portal in 4.1 - April 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. Curious about the latest updates in the Jira Service Desk Server...

416 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you