Is ScriptRunner's Behavior config written out to workflow json during workflow export?

Is ScriptRunner's Behavior config written out to workflow json during workflow export?

1 answer

1 accepted

2 votes

No, it's not part of any workflow... the same behaviour can be used across multiple different projects and workflows, which is quite a common use case. Although it's often related to a workflow, it doesn't have to be.

The configuration is stored in the general morass of jira's database... so it's there if you do backup/restore, or duplicate to another system. 

Too bad. I'm currently developing a new workflow using ScriptRunner and Behaviour on my test server. Once completed I will transfer the workflow to our production server and then migrate the existing projects to it. Any suggestions to make my life easier?

If you click on the Edit link by the behaviour, it will show you the behaviour as XML. You can paste that in to a new behaviour on the other system. But take care with custom field IDs.

Painful but doable...thanks

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

102 views 0 2
Join discussion

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