Issue board with multiple groups and/or projects scope
Problems
- For personal workflows, I want to be able to see issues across the entire instance, and manage them myself. The issue dashboard itself is helpful but limiting, because it just presents a list of issues assigned to me. I need a more flexible way to organize those issues.
- For team workflows, if a team works across multiple groups, they currently don't have a way to organize that work together.
Concept
- Extend our existing group-level issue boards so that for a given group board, it can be scoped to have additional groups.
- I.e. there is a special configuration. For a group board in group
A
, the default scope are issues in projects that are in the group tree structure rooted at groupA
. But there is now a special configuration where you can also pull in scope from another group, such as groupB
, and specify it in that group board.
Scope
- Issues: All the issues from all projects from all the groups (including their descendants) specified above form the issue scope of the issue board.
- Labels: All the labels from all projects and all groups (including their descendants) specified above are available in the board, whether as filters, as board config, or as label lists.
- Milestones: Similar to labels above.
- Users: All the users from all projects and all groups (including their descendants) specified above can access the board itself.
- Permissions: A user who views the group can see only what they are supposed to see. I.e. if they don't have access to a certain issue, it shouldn't appear for them in the board. If they don't have access to a label or a milestone, then those associated label lists or associated milestones lists shouldn't appear for them.
Edited by Victor Wu