Skip to content

Re-work navigation for GitLab > Operations

Problem to solve

Right now, we have a pretty large list of items under Operations:

Screen_Shot_2020-03-16_at_11.18.44_AM

We currently have eight items, with another possibly forthcoming as we add an alerts manager into the UI.

Currently, Operations is used as a holding ground for most Monitor and Configure items. But, the list order feels like it's not quite right currently (for example, Logs is separate from Metrics and Tracing, even though the three are closely linked to Observability). Perhaps we should investigate if the current ordering makes sense, or if it should be cleaned up a bit?

Intended users

Further details

Proposal

We have two proposals here, and we want to get feedback on which is the right way forward.

Option 1: Separating out the current Operations tab into Operations and Infrastructure

Operations Infrastructure
Operations_Navigation_-Solution_2-_Operations Operations_Navigation_-Solution_2-_Infrastructure

Option 2: Separating out the current Operations tab into Operations, Infrastructure and Environments

Operations Environments Infrastructure
Operations_Navigation_-Solution_1-_Operations Operations_Navigation_-Solution_1-_Environments Operations_Navigation_-Solution_1-_Infrastructure

Option 3: Creating a new releases section, and adding Environments to it

Operations section Infrastructure section Releases section
Operations_Navigation_-Solution_3-_Operations Operations_Navigation_-Solution_3-_Infrastructure Operations_Navigation_-Solution_3-_Releases

Figma File

Permissions and Security

Documentation

Availability & Testing

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

Original Mural mappings

Edited by Amelia Bauerly