MVC: Expose Environments at Group Level

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

Currently there is no way to roll up all environment deployments across a given group within GitLab - the Operations and Deployments dashboards are user specific and will not show new projects nor group deployments per environments. This oftentimes leads the "ordering" of environments to not be intuitive.

👆🏻 notice how the order of production vs staging is sorted on an environment's primary key.

Intended users

• Delaney (Development Team Lead)
• Devon (DevOps Engineer)
• Allison (Application Ops)

User experience goal

At a given group, users ought to be able to see (by environment) deployments across all applications for that given group.

Proposal

for a given group/subgroup...

1. Group on Environment Name (not URL - as this will support more than just microservice architectures)
2. Exclude any namespaced environments for MVC (review/app-1 would be ignored)
3. Exclude any deployments from projects within subgroups (GraphQL limitation)
4. Limit to 100 projects (GraphQL limitation)
5. Provide users links to the actual environment pages for each given project.

I've recorded a <4min video on what the experience would be like (granted it did include the Commit SHA which I've now undone).

More details can be found within epic discussion.

Permissions and Security

Documentation

Availability & Testing

Available Tier

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references