-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
9
-
Issue Summary
The list of possible parents for an issue does not always include the issues from the same project. This is a change in behaviour to the epic link field.
This only affects company managed projects.
This is reproducible on Data Center: No
Steps to Reproduce
- When creating or editing an issue, click into its parent field
- Review the list of potential parents suggested by JSW
Expected Results
Issues in the same project as the child should be prioritised towards the top of the list.
Actual Results
Issues from any project that the current user can view issues for are loaded. Initially they are prioritised by last viewed date, updated date and priority. For subtasks, issues on the BASE level are listed before those on higher levels. For non-subtasks, issues in the same project that were part of the initial grouping are listed first.
Workaround
Limiting the 'Browse Projects' permission to a particular project will help.
- is duplicated by
-
JRACLOUD-92271 Prioritize Epics from the same project at the top of the dropdown list in the Parent Field.
- Closed
- mentioned in
-
Page Failed to load
- relates to
-
PCS-235240 You do not have permission to view this issue
[JRACLOUD-92269] Prioritise parents in the current project when suggesting possible parents for an issue
UIS | Original: 2 | New: 3 |
UIS | Original: 3 | New: 2 |
UIS | Original: 1 | New: 3 |
Support reference count | Original: 8 | New: 9 |
Support reference count | Original: 14 | New: 8 |
UIS | Original: 2 | New: 1 |
Component/s | Original: Issue - Hierarchy and Parenting [ 78001 ] | |
Component/s | New: Issue - Hierarchy and Parenting [ 77928 ] | |
Key | Original: JSWCLOUD-26162 | New: JRACLOUD-92269 |
Project | Original: Jira Cloud [ 18511 ] | New: Jira Platform Cloud [ 18514 ] |
UIS | Original: 1 | New: 2 |
Support reference count | Original: 13 | New: 14 |
Component/s | Original: Epic renaming [ 72991 ] |