Project and issue management

[rdeltour]

To help us triage the issues and have an overview of milestones and development phases, we could rely on built-in GitHub projects or any of the more advanced alternatives like Waffle, Zenhub, Huboard, etc.

What we're looking for:

• management of issue dependencies (e.g. issue X depends on issue Y)
• concept of "meta issues" or "epics" (e.g. an issue that is a collection of other issues)
• easy triage in a kanban-style column view

What we don't need:

• support for multiple repositories

Constraints:

• the tool must be accessible, or alternatively all the info must be accessible from Github's native issue tracker

Do we want to use such a tool? Would it be helpful to the steering committee?

[TzviyaSiegman]

I would find it helpful. I am fine with GH Projects, but I do find the manual nature a little annoying sometimes.

[tofi86]

the tool must be accessible, or alternatively all the info must be accessible from Github's native issue tracker

I think this is hard to achieve. Do you know of any tools with such a tight integration?

What we're looking for:

Better tools for issue triaging would be fine. Epics, meta, etc. But in the end, I think we could live with the native GitHub tools, don't you think?

We don't have that much traffic in the project here, so creating Epics can be a convention like adding [EPIC] to an issue title and adding a label and then linking issues to the epic manually.

I know, it's kinda hacky, but I fear the overhead of a second tool.

[tofi86]

FYI: GitLab IMHO has better issue triaging tools, but we would have to move the whole project to gitlab.com

[rdeltour]

the tool must be accessible, or alternatively all the info must be accessible from Github's native issue tracker

I think this is hard to achieve. Do you know of any tools with such a tight integration?

FWIW, some of the tools rely on issue labels, so all the information can be retrieved from the regular tracker.

But in the end, I think we could live with the native GitHub tools, don't you think? We don't have that much traffic in the project here, so creating Epics can be a convention like adding [EPIC] to an issue title and adding a label and then linking issues to the epic manually. I know, it's kinda hacky, but I fear the overhead of a second tool.

A column view is a useful tool for managing a work plan, and the native GitHub projects unfortunately make that a bit painful (despite the new "automation" possibilities, it's still very limited and not flexible). For instance, just populating a new project with all the issues from a single milestone is a hassle; or filtering an existing project per label or milestone is impossible (AFAIK).

But yeah, I do fear the overhead too 😄 Let's think this through.