...
If things are not working as expected, it can often be resolved by being careful with the configuration and looking at errors produced. Some time Sometimes more detailed problem determination information may need to be sent in.
| Tip | ||
|---|---|---|
| ||
See Tips. |
Initial Steps
- Double-check your configuration together with looking at various how to's.
- Make sure you are using substitution variables correctly.
- Are all required fields provided?
- Does the user that will run the transition have permission to do the configured actions?
- Look through your server log for entries indicating various problems that can occur during a transition. The log is the only place some of these errors can be reported. This is especially true for problems with custom fields. Error entries are logged for most situations that cannot be completed as expected. A post function runs after the transition has occurred, so error logs are really the best way to indicate that some things may not have been done based on the situation. If you add INFO logging (see the steps below), you will get some more detail explanations of what is happening with conditioning and other features.
- If still a problem, open an issue with information on your configuration, JIRA version, and add-on version.
- If it is a custom field-specific issue, indicate what type of custom field is causing problems. Not all custom field types are fully supported - see Custom Field Types.
- In most cases, that will be sufficient to resolve the issue. In some situation situations, more information may be needed. For instance, you can attach your exported workflow. In more difficult cases, you may be instructed to collect debug information. These are the steps to follow. You will need access to the JIRA server log file.
...
The easiest way to provide configuration information is to take a screen shot screenshot of the post function configuration. Go to the view post function screen and capture one or more post function views:
...