Don't group issues by project on group-level and dashboard issue indexes.
When sorting by priority, we expect to see a single ordered list, so that developers can working on issues starting at the top. Right now, the list is split up across projects (gitlab-ce and gitlab-ee in our gitlab-org case), with one list for each project, which makes it seem like a relatively unimportant issue in the first list is more important than a top priority issue in the second list, because that's how the lists are ordered.
An example can be seen on https://gitlab.com/groups/gitlab-org/issues?assignee_id=0&label_name%5B%5D=Platform&milestone_title=8.14&scope=all&sort=priority&state=opened:
~P2 and direction are both higher priority than either of ~"Community Contribution", ~Platform or ~"feature proposal"
I would like to prioritize this for %8.14, because it would make it a lot easier for our people to find issues to work on in the actual priority we intend.
Proposal
Remove project grouping on group level indexes and add the group path to the issue ID if applicable.
- For multiple groups on a page:
group/project#issue-id
- For one group, multiple projects:
project#issue-id
- For one project:
#issue-id