When grouping similar environments, environments aren't shown if they share the name of the "root" environment

added customer devopsrelease [DEPRECATED] environments priority4 severity3 typebug + 1 deleted label

I think this may be gitlab-ce~3412464. /cc @filipa

It is not @deandre, they are sent in a group by the backend

I'm not 100% sure this is a bug though - @grzesiek are you able to confirm? Thanks!

Looks like a bug, yes.

added Category:Release Orchestration label

Setting gitlab-ce~~10690712 based on gitlab-ce~~8482045.

added grouprelease [DEPRECATED] label

Set milestone to backlog as it is a P3 bug

@cstasik FYI - we want to solve all P2 bugs in 12.3 & 12.4 - you may want to consider this one for a further release as it is a customer bug

changed milestone to %Backlog

@ogolowinski Thanks, I am adding to %12.4 for customer impact and we can prioritize it with the gitlab-ce~~3857523 gitlab-ce~~2278648 list and adjust based on capacity, severity as that point.

changed milestone to %12.4

added [deprecated] Accepting merge requests label

@cstasik As the P2 bug count has increased, I doubt they will get to it in 12.4, 12.5 or 12.6 seems more reasonable

@darbyfrey let me know your thoughts on the best milestone to place this for now based on capacity. I placed %12.4 but let me know if it should move out.

Let's evaluate this one when planning for %12.4 and we can move if necessary

added 1 deleted label and removed grouprelease [DEPRECATED] label

changed milestone to %12.4

Changed label to Category:Continuous Delivery

added Category:Continuous Delivery label and removed Category:Release Orchestration label

mentioned in issue #34385 (closed)

added missed:12.4 label

Moving to Backlog as this issue is a P4, @darbyfrey Please change the milestone if you disagree

changed milestone to %Backlog

added missed-deliverable label

removed 1 deleted label

added to epic &3294 (closed)

added sectionops label

added Category:Release Orchestration label

We have an Ultimate customer affected by this - https://gitlab.my.salesforce.com/0016100001ZxeQv

Each of their projects have multiple environments:

Review
Dev
Staging
Production
BCP

Each of these environments have multiple deployments (usually the application aswell as a sidekiq deployment). When i navigate to Operations > Environments in the Gitlab UI and expand these environments, I can only ever see n-1 deployments. Example, if i have 3 deployments in the environment the UI will let me see 2 only. If i have 2 deployments in the environment the UI will let me see 1 only. (See screenshot).

This is impacting our ability to easily see all of our environments

@pharlan any chance you can add the screenshot in slack?

marked #20574 (closed) as a duplicate of this issue

marked this issue as related to #20574 (closed)

mentioned in issue #20574 (closed)

added grouprelease [DEPRECATED] label and removed 1 deleted label

changed epic to &5304 (closed)

mentioned in issue gitlab-org/ci-cd/release-group/release#65 (closed)

added UX frontend labels

added 1 deleted label

ZD: https://gitlab.zendesk.com/agent/tickets/278196 (internal)

mentioned in epic &7682 (closed)

added backend label

@cbalane @rayana I looked into this a bit today, and it looks like it can primarily be fixed via the backend.

Here, we can see in the response the size for review is 2, but we have no way of knowing that there should be a review and review/foo environment, only that this is likely a folder. Later, when we fetch the folder, we don't get the review environment, only the review/foo one.

Nice! Thanks for following up, @afontaine.

I'm assuming that in the UI, we would be able to display an item for the review environment, that shows the latest deployment. And below that, a folder for review/, with all other scoped environments?

@rayana we push folders to the top of the sort order, but yes, I think that is ideal.

@rayana I'm assuming you don't need any additional review here, so adding it to our queue for weighting. Please update if that's not correct.

@nicolewilliams Sounds good. This issue is an actionable insight from https://gitlab.com/gitlab-org/ux-research/-/issues/1841.

Andrew and I reviewed it some weeks ago. There are a couple of ways the root environment can be surfaced in the UI -- I added a boring solution to the proposal.

Depending on how we decide to proceed with the UI changes, the way environments are displayed on this page might change in the near future and this UI will require refactoring -- so it's good to keep that in mind.