---
title: "Tips"
canonical: "https://support.appfire.com/space/CW/69304761/Tips"
format: markdown
---
### References

- [Configuring Workflow](https://confluence.atlassian.com/display/JIRA/Configuring+Workflow) - basics on how to configure a workflow so you can take advantage of the features of this add-on
- [Advanced Workflow Configuration](https://confluence.atlassian.com/display/JIRA/Advanced+Workflow+Configuration) - know the difference between conditions, validators, and post functions

> ✅ ### 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](https://appfire.atlassian.net/wiki/spaces/GINT). 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](https://appfire.atlassian.net/wiki/spaces/CW/pages/69304737).

> ✅ ### Using JQL
> ✅ 
> ✅ The JQL support provides some powerful conditioning and substitution support. Test your JQL in interactive JIRA first. If you use [substitution variables](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68748151) for the JQL, double quote values that may (on substitution) contain blanks.

> ✅ ### Custom fields not changing
> ✅ 
> ✅ 1. Make sure the custom field is defined for the issue type you have
> ✅ 2. Make sure it is on the supported [Custom Field Types](https://appfire.atlassian.net/wiki/spaces/CW/pages/69304703) when using **set**. Use one of the **copy** custom fields instead if appropriate. Otherwise, open an issue to get support for unsupported types.
> ✅ 3. [How to get problem determination information](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68748362)