Versions Compared

Old Version 12

changes.mady.by.user Deborah Scott

Saved on

compared with

New Version 13

changes.mady.by.user Pooja Gopalnaidu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

References

Tip

Test your workflow!

Workflows can be complicated (smile). 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 (smile).

...

Tip

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 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

Tip

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 (smile). 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.

...

Tip

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.

Tip

In some cases, ordering the post function may improve related behavior.

  1. Greenhopper rapid board - CSOT-87

  2. Avoid indexing bug - JRA-31775 on pre Jira 6 systems - see CSOT-78