Details
-
Bug
-
Status: To Do
-
High
-
Resolution: Unresolved
-
4.3.19
-
None
-
None
-
2.4
Description
Scripted conditions evaluated during a fast track transition don't get the updated values of fields that were on the workflow screen.
Steps to reproduce:
1) On one workflow transition (say "To Do"), add a screen that lets you update a field (for example, priority). On the same transition, put a post-function that fast tracks the issue to another status (say, "In Progress").
2) On the transition to "In Progress", put a simple scripted condition that is based on the field you added to the workflow screen (e.g. issue.priority?.name == 'Medium').
3) Publish your workflow.
4) Find an issue in your instance and edit the example field to be a disallowed value (e.g. priority = Low).
5) Transition the issue through the first workflow step (e.g. To Do). Edit the example field to an admissible value (e.g. priority = Medium).
The transition will fail, as the scripted condition is evaluated based on the old value.
Attachments
Issue Links
- relates to
-
SRJIRA-2189 Assignee is not set in behaviours if user picker returns multiple results and the required user is not the first one
-
- Done
-