.png?version=1&modificationDate=1657805719617&cacheVersion=1&api=v2&width=272&height=48)
References
Configuring Workflow - basics on how to configure a workflow so you can take advantage of the features of this add-on
Advanced Workflow Configuration - know the difference between conditions, validators, and post functions
User experiences and tips
Test your workflow!
Workflows can be complicated 
. Define a reasonable test scenario for your workflow on a test project or test system. Often, it is the only way to find errors before putting your workflow in production. Consider formalizing your workflow testing with GINT - Groovy Integration Test Framework. In the future, a simple GINT workflow test example will be provided .
Errors
Post functions are run after the transition has already occurred - there is no turning back. If your post function has configuration errors, the Jira server log is the only place those will be reported. When testing and debugging your workflow configuration, make sure you have access to the log and ensure your changes have not introduced unnoticed errors. If necessary, follow How to get problem determination information.
Using JQL
The JQL support provides some powerful conditioning and substitution support. Test your JQL in interactive Jira first. If you use substitution variables for the JQL, double quote values that may (on substitution) contain blanks.
Custom fields not changing
Make sure the custom field is defined for the issue type you have
Make sure it is on the supported Custom Field Types when using set. Use one of the copy custom fields instead if appropriate. Otherwise, open an issue to get support for unsupported types.
Subtask have different issue types
You cannot create a sub-task with the same issue type as the parent since Jira has unique sub-task issue types . You can do something similar by using a naming convention that creates sub-task types with similar names. For instance, Bug and Bug-sub-task. Then the %parent_issuetype%-sub-task can be used to create a sub-task with a name related type.
Post function ordering
It is important for workflow designers to understand how the order of processing can affect results. Some actions will not behave properly if done in the wrong sequence. Think carefully and try alternative ordering in your tests.
In some cases, ordering the post function may improve related behavior.
Greenhopper rapid board
Avoid indexing bug on pre Jira 6 systems
