Group and subgroup cycle analytics
Organizations that use multiple projects will likely have teams that works amongst multiple projects. In the same way that group issue and merge request lists are useful for understanding work across multiple projects, it would be useful to be able to access cycle analytics information at a group level.
For example at GitLab the work of a team may be split across gitlab-org/gitlab-ce and gitlab-org/gitlab-ee. This makes it hard to reason about cycle analytics on a team level, or understand cycle analytics at an organization level.
Proposal
- Make cycle analytics available on groups and sub groups level
Links / references
Documentation blurb
Overview
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml