Details
-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
9
-
Severity 2 - Major
-
0
-
Description
Description
Since the latest JIRA release (v7.0.0-OD-02-247), whenever the user try to create a new Post function of type Update Issue Field, the text shown on the issue Post function does not always reflect the Post function created.
Examples:
Updating the Assignee:
The Assignee of the issue will be set to $textutils.htmlEncode(${fieldValue}).
Updating the Priority/Resolution:
- If there's a Condition set in the same Workflow, the message displayed in the post function will be the same as the condition:
ConditionOnly users in project role Service Desk Team can execute this transition.
Post function
Only users in project role Service Desk Team can execute this transition.
- If there's no Conditions, then the message displayed changes to:
Type: class Class: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction Arguments: field.name = priority full.module.key = com.atlassian.jira.plugin.system.workflowupdate-issue-field-function field.value = 4
It's impossible to re-order the Post functions when their descriptions match the condition set, but if the post function is displaying the type and class, reorder is possible again, however, if the reordering is done, the post function will mimic the behaviour of the exact above post function.
Steps to reproduce
- Create a condition in any workflow.
- Create a post function of type: Update Issue Field to change the resolution field, for example.
Expected
The post function have its name and its properties.
Actual
The post function mimics the behaviour and properties of the conditions set.
Attachments
Issue Links
- details
-
JRACLOUD-65768 Workflow post functions displaying incorrectly.
- Closed
- is duplicated by
-
JRACLOUD-65653 List of post functions for workflow transition shows wrong description
- Closed
- is related to
-
JSWSERVER-13143 Agile Simplified Workflow transition In Progress displays the post functions incorrectly
- Closed