Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
None
-
Severity 3 - Minor
-
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
I am using JIRA Cloud and noticed that components are sorted by ASCII order, not alphabetical order, when determining the default assignee of a newly created bug. This contradicts the documentation at https://confluence.atlassian.com/jira/defining-a-component-185729533.html . That documentation states:
```
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.
```
Reproduction steps:
1. Create a component called 'a'
2. Create a component called 'B'
3. Assign Person 1 as the default assignee for component 'a'.
4. Assign Person 2 as the default assignee for component 'B'.
5. Create a new bug that affects both the 'a' and 'B' components.
6. Person 2 is now the assignee for the bug, rather than the expected Person1.
Attachments
Issue Links
- relates to
-
JRACLOUD-46283 When determining default assignee, components are sorted by ASCII order, not alphabetically as documented.
- Closed