-
Bug
-
Resolution: Fixed
-
Medium
-
17
-
Severity 2 - Major
-
1
-
Summary
On a setup where 2 similar workflows are configured within the same workflow scheme, the property from one workflow is taking effect on issue types that are not assigned to that workflow.
Steps to Reproduce
- Create a duplicate workflow (Workflow_1 and Workflow_2) containing To Do, In Progress, Done status.
- Set up the following workflow scheme :
Name Issue Types Workflow_1 Story, Epic, Tasks, All Unassigned Issue Types Workflow_2 Bug, Sub-tasks
- Assign the workflow scheme to a project.
- Edit the workflow property for In Progress status for Workflow_1.
- Add the property jira.permission.work.denied and blank value (property to disable worklog on the workflow).
- Try to use "Log Work" for a Story and try to use "Log Work" for a Bug.
Expected Results
Log work should not be available for any issue type on In progress status except for Bug and sub-tasks.
Actual Results
Log work is disabled for Bug and sub-tasks even if Workflow_2 has not property to disable it.
WORK_ON_ISSUES granted by permission scheme but DENIED by workflow
The workflow property that will take effect is the one from the workflow which is assigned to All Unassigned Issue Types.
- is duplicated by
-
JRACLOUD-67705 Status property key unintentionally applies to multiple workflows
-
- Closed
-
-
JRACLOUD-68864 Workflow status properties being applied to all workflows inside a workflow scheme
-
- Closed
-
- is related to
-
JRACLOUD-67154 Workflow property jira.permission.work
-
- Closed
-
- relates to
-
JRACLOUD-67800 Workflow status properties are not working
-
- Closed
-
-
DONUT-2461 Loading...
- mentioned in
-
Page Loading...