Versions Compared

Key

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

 🤔 Problem Description

Transitions might have the same name but different JSU validators, conditions, and post functions, which might lead to confusion.

...

  1. The JSU post functions/conditions or validators are not being executed because the wrong transition is used.

  2. Workflow administration becomes challenging if the transitions with the same name aren’t properly documented.

  3. The Jira issue might not follow the expected path in the workflow because of the confusing transition button options.

🌱 Solution

To avoid this problem, it is important to consider the following:

  • When creating transitions in a custom workflow, avoid using the same transition name for different purposes.

  • If you need to use the same transition in other statuses in the same workflow, prefer to reuse the transition instead of creating a new transition with the same name.

  • If you need the same transition to perform different actions, for example, depending on the state, a JSU post-function, condition, or validator, prefer different transition names to avoid confusion.

Filter by label (Content by label)
page
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@bc3e0baf
maxCheckboxfalse
showSpacefalse
sortmodified
showSpacetypefalsepage
reversetruetype
labelskb-how-to-article
cqllabel in ( "jsu-action-transition" , "jsu-best-practices" , "jsu-product-jira" ) and type = "page" and space = "SUPPORT"labelskb-how-to-article