Versions Compared

Old Version 8

changes.mady.by.user Sireesha Dugginapeddi [Appfire] (Inactive) (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Pooja Gopalnaidu

Saved on

Key

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

References

Tip
title

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.

title
Tip

Errors

Post functions are run after the transition has already occurred - there is no turning back. When you see your post function not working as expected, and you want to check if it is due to a configuration error, go through the log messages in the Transition logs page. This is the go-to place to understand what went wrong.

Tip
title

Custom fields not changing

  • Make sure the custom field is defined for the issue type you have.

  • pen

    Make sure it is one of the supported Custom Field Types when using set. Use one of the copy custom fields instead if appropriate. Otherwise,

    o

    open an issue to get support for unsupported types.

Tip
title

Subtask have different issue types

You cannot create a subtask with the same issue type as the parent since Jira has unique subtask issue types (smile). You can do something similar by using a naming convention that creates subtask types with similar names. For instance, Bug and Bug-sub-task. Then the %parent_issuetype%-subtask can be used to create a subtask with a name related type.

Excerpt
hiddentrue
nameGuides

Tutorials

Use this link to find all tutorials available in the Create on Transition for Jira documentation.