Epic checklists
I have been using Epics for a while now, and meta issues even longer and I'd really like epics to behave more like my usage of meta issues. One specific way is handling of checklists of issues. I've used the description of a meta issue to keep track of issues grouped by milestone.
https://gitlab.com/gitlab-org/gitlab-ce/issues/38366 is a good example of one of the consistent usage patterns.
Several things worth noting:
- There are multiple named checklists consisting of issues and their open/closed status.
- Most of the lists are named for their milestone.
- Some lists have more verbose names like identifying which milestone is going to be GA.
- There's usually a Future list as well.
- It would be OK if all checklists appeared at the bottom of the description, for example instead of the Related Issues section.
- It's important for readability that each list item be one line high. The Related Issues list with two lines, a separator, and lots of vertical space ruins the use case.
- Now that issue references include
(closed)
, we've fallen into a pattern of copying the issue title and adding a colon and then the issue URL. I'd rather just put in the issue URL and have the title automatically kept up to date. - I'd rather the item checkbox status be automatically synced with the issue status.
- When issues are moved to another repo, the description should be updated to point to the new issue with the correct status (moved issues are really misleading as closed)
- Trello does pretty much this exact thing (minus showing issue status)