Move Cohorts out of instance statistics

Overview

With #196455 (closed) and #196454 (closed), we can start hiding Instance Statistics in the top navbar when this feature's admin-only.

We're not confident that Instance Statistics, as currently displayed in the navbar, is the right place for these features to thrive. We should consider moving them elsewhere or refactor the Instance Statistics area into a more useful tool.

Proposal

• Move Cohorts to the admin panel (#233833 (closed)).
• Update the documentation for how to navigate to Cohorts.

changed milestone to %Backlog

added devopsmanage groupoptimize labels

@npost: I mentioned in #196455 (comment 288621556) that moving Value Stream Analytics and Productivity Analytics out of the Instance Statistics area will make IS more or less invisible to non-admins.

This issue considers how we can remove the remaining two features. Is there a place we can move these two features - or can we prove out a vision for the Instance level area dropdown you mocked up elsewhere and iterate in that direction?

added UX backend frontend labels

added [deprecated] Accepting merge requests label

@jeremy is the problem here that the navigation is advertising a feature to all users which is a dead-end for all accept admins? Are there other motivations for this?

@jshackelford: Both of these features present in an "Instance Statistics" area presented in the top navbar: https://docs.gitlab.com/ee/user/instance_statistics/

• These are the only 2 features that are present in this view, so the left navbar winds up looking pretty spartan and unmaintained.
• The top navbar is quite crowded and hard to make responsive. At the moment, some features are being piled into the "More" dropdown which is suffering from "junk drawer" syndrome.

There may be a place that we need to consider placing instance-level type features, but I think it requires some additional thought. Since I wasn't aware of significant usage behind these remaining features (Cohorts and DevOps Score), I suggested we remove the top icon for now.

A (better) alternative would be doing some design thinking around the right place for these instance-level, more sophisticated capabilities and move them there instead.

changed the description

changed the description

mentioned in merge request !28152 (closed)

mentioned in merge request !28153 (merged)

I'm interpreting this as "eliminate the Analytics Workspace," so I've added some cleanup aspects to the proposal (e.g. documentation and navbar).

changed the description

marked this issue as related to #223734 (closed)

mentioned in issue #223734 (closed)

mentioned in issue #224146 (closed)

@jeremy In our conversation with John Woods he suggested:

Cohorts is not specific enough and requires too much API work to be actionable or useful.

Which makes wonder if it is worth moving or if we ought to just start the process of deprecating it. Are you aware of loyal users?

I'm not confident that we should deprecate it. The main use case I'm aware of was Customer Success using it to help customers understand their user activity.

It needs improvement, but I don't think that means we throw it out. I also think @amandarueda on Fulfillment was thinking about improving it. I don't think we should remove it from the application.

If our new Analytics telemetry comes back with very low usage of this page, we can definitely reconsider

I agree, I'd like to see use make the cohorts page useful rather than removing it completely. I thought I had opened an issue for this but am not able to find it. I've created a placeholder here: #224691 (closed)

changed the description

mentioned in issue #224717 (closed)

changed title from Move Cohorts and DevOps Score out of instance statistics to Move Cohorts out of instance statistics

Perhaps we could split [this Cohorts/Devops Score combination issue] and start on the Cohorts move. (source)

@jshackelford good idea. Discussion on this issue seems to have been more focused on Cohorts, so I just moved the Devops Score aspect to a new issue: #224716 (closed).

Awesome, thank you.

marked this issue as related to #224717 (closed)

marked this issue as related to #224716 (closed)

mentioned in issue #224716 (closed)

added to epic &3726 (closed)

mentioned in issue #193435 (closed)

changed the description

added Next Up label

added workflowplanning breakdown label

changed milestone to %Next 1-3 releases

mentioned in issue gitlab-org/manage/general-discussion#17258

marked this issue as related to #233833 (closed)

@jeremy @npost @djensen I believe this is currently blocked by #233833 (closed) which needs to be implemented first. Thoughts?

Agreed. Is it possible to estimate this with that issue in mind?

@pshutsin could you estimate this one please? (Understanding it's currently blocked by #233833 (closed).)

added workflowblocked label and removed workflowplanning breakdown label

set weight to 2

changed milestone to %13.4

mentioned in issue #233833 (closed)

mentioned in merge request !39368 (merged)

added priority2 label

removed Next Up label

added priority3 label and removed priority2 label

added sectiondev label

This issue is being solved in !39368 (merged), therefore I'm moving it to workflow:in review (documentation comes in a follow up MR). /cc @djensen @wortschi

added workflowin review label and removed workflowblocked label

assigned to @m_frankiewicz

mentioned in merge request !39855 (merged)

removed [deprecated] Accepting merge requests label

Both code changes !39368 (merged) and docs updates !39855 (merged) MRs have been merged, so I'm closing this issue.

closed