Is ScriptRunner's Behavior config written out to workflow json during workflow export?
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Painful but doable...thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.