Unintuitive epic order in boards grouped by epics
### Summary Epics in boards grouped by Epics seem ordered by decreasing created date which is counter intuitive. I would rather have the ability to manualy order epics or (which could be the default) have them order by label priority or closest milestone due dates. ### Steps to reproduce 1. Start with a board with one list and two issues"One" and "Two", manually ordered in that order 2. Create Epic A and set issue "One" to that Epic 3. Create Epic B and set issue "Two" to that Epic 3. Refresh the board and group by Epics : the Epic A will be below the Epic B. I have found no way of changing that order, either by manually sorting Issues, or by setting prioritized labels to Epics. ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? In boards grouped by Epics, the Epic order is sorted by the Epic creation date, and is not changeable by any means (or at least I haven't found any way of doing it). It is common for us to create batch of Epics by decreasing priority, starting with the first upcoming Epic and ending with the lowest priority. The board will therefore sort Epics in reverse order for us. ### What is the expected *correct* behavior? I would rather have the ability to manualy order epics or (which could be the default) have them order by label priority or closest milestone due dates. #### Results of GitLab environment info This happens on a hosted Gitlab, for a Premium user, with version 13.10.0 (up to date as of today)
epic