Issue boards can't be used for both Product and Development

Description

Group Issues board scoped to a team label can be really useful for a development workflow using ~"In dev" and ~"In review" lists:

  • as a developer you can quickly see what task you have to work on for current iteration and easily update it's state (Kanban style)
  • as a manager you can quickly see the global progress of the team at any time

e.g. for ~"Security Products" we'd like to use 11.0 Security Products - DEV

Though in the current implementation it seems that when an issue is closed all labels that are used in any board's list are removed.

And unfortunately there are other existing boards like Next 2-3 months or X.Y Planning that have team labels as board lists.

This ends up with having the team label to be removed when closing an issue in our DEV board, which is not the desired behavior.

Demo

boards

Proposal

Having this drag and drop feature makes the board clearly looking like it's made for this state transition usage and there is also an open issue to make the close button on issue's page to also remove the labels used in board lists to have a consistent behavior, which I also find is a relevant behavior.

So I think we need to find another way to provide this cross teams "Product" or "Planning" view and do not use team label in board lists.

If we agree on that it should then be added to the handbook and the workflow labels documentation

Edited May 11, 2018 by Olivier Gonzalez
Assignee Loading
Time tracking Loading