-
Bug
-
Resolution: Fixed
-
Low
-
None
-
8.4.0, 8.2.4, 7.13.6, 8.3.3
-
None
-
7.13
-
1
-
Severity 3 - Minor
-
Issue Summary
When issue has multiple components, the default assignee is not set as Unassigned, when following the rule assignee will be set to the default assignee of the component that is first alphabetically, rule
Environment
8.2.4 8.4
Steps to Reproduce
#Create a new project
- set Default Assignee - Unassigned
- Add components
Mac Book, Lead - Mark, Assignee - Component Lead
Dell, Lead - Dave, Assignee - Project Default - Create issue with components Dell and Mac Book
- Check Assignee it will be set as Mark
Expected Results
The Assignee should be Unassigned as stated in Managing components
_ If an issue has multiple components, and the default assignees of components clash, the assignee will be set to the default assignee of the component that is first alphabetically._
Actual Results
Assignee set is as Mark
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available