Our project has an extensive backlog and as PM it is very helpful to keep the backlog up to date based on priority. We work in two-week sprints, but during a sprint we might drop out one issue in favor of another. Our way of work uses parts of Scrum and Agile. I want to make sure the issues we have in our backlog are ordered (combination of priority and severity) so whenever a sprint is cleared, a team member can pick up a new issue right away that is on top of the list without asking me if that’s best next thing on the list.
We used to work with labels and their priorities. This works, but it’s not ideal. Recently I’ve discovered the Manual sorting option and it was exactly what I needed. Before Gitlab, I worked on a project for a couple years that used JIRA. What I liked most about JIRA was the infinite scrolling list, able to create sections of tickets, and prepare before sprints. I use the Milestones in Gitlab to prepare for sprints now but it’s still less ideal than JIRA. I’m flexible and don’t expect to copy my JIRA way of work, backlog grooming, and sprint preparation onto Gitlab, but there are a couple things that
I’m wondering if I’m overseeing parts of Gitlab or if I have to do with the possibilities that I have in the situation we work in.
- Once sorted by using the Manual option, I can’t drag and drop issues between pages. Is there a way to have all issues on one page for example? Currently I have to add a label to new issues, drag and drop those new issues above an issue which is higher on the list and then remove the label again. It doesn’t feel like the right way of doing and is quite cumbersome. When a new issue is created, I’d like to drag and it to the top of the list by myself (or as in JIRA -> right-click -> ‘Move to top of backlog’ -> drag to the right position from there). It is mentioned in the issue introducing the feature, but was left out of development I guess. Another follow up issue was created to introduce the ‘move to top / bottom’ button, but no updates for a couple months.
- Are there any documents that explain the ‘ideal’ usage of issue lists in Gitlab? I have found similar documents about labels and how Gitlab is used internally, but not for issue lists per se.
- Are there any blogs or articles about other PMs who do backlog grooming in Gitlab you’d recommend reading?
Ideally I’d just want one long list of all issues that I can divide into sections: top part is for next sprint, another section for issues that I’d like to have for the sprint after that, backlog with other issues below that I have prioritized.
Any input is welcome, thanks in advance!
P.s. Sorry, just realized this is the wrong subforum as this is not about configuring / installing Gitlab itself. Was redirected here from the Help-section.