Unclear/Incorrect Label Priority Resolution in Group Hierarchy
Summary
Group labels and their prioritization are not resolved correctly in nested groups.
Steps to reproduce
- Create a group
root-group - Create a sub-group
child-groupunderroot-group - Create a project
root-projectas member ofroot-group - Create a project
child-projectas member ofchild-group - Create two labels
prio:0,prio:1as group labels underroot-group - Go to labels view of
root-project, star the labels and prioritize them - Create some issues in
root-projectusing these two labels - Create some issues in
child-projectusing these two labels
What is the current bug behavior?
- Go to issues view of
root-group, select Label Priority for ordering
You will note that only the issues from root-project will be ordered according to their labels' priorities; label priorities are not propagated down the group tree (or bubbled up to the root group's issue view). This might be due to the prioritization being only set on project level, not on group level.
Even if you would reproduce the same labels with same names as group labels under child-group and also prioritize them in child-project, their respective priorities will not be taken into account in the label ordering on root-group's issues view. If group labels of child-group are prioritized in child-project, even the issues view with Label Priority ordering on child-group would not order the issues according to the assigned label priority order.
What is the expected correct behavior?
When listing all issues in the issues view of root-group and ordering them via Label Priority, I would expect that all priorities (also those defined on deeper group levels) would be taken into account for ordering.
When listing all issues in the issues view of child-group and ordering them via Label Priority, I would expect that the priorities would be taken into account for ordering at all.






