Merge branch 'master-patch-cc81' into 'master'

Cells impact on Your Work

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/129109



Merged-by: Thong Kuah <tkuah@gitlab.com>
Approved-by: Mike Nichols <mnichols@gitlab.com>
Approved-by: Thong Kuah <tkuah@gitlab.com>
Co-authored-by: Christina Lohr <clohr@gitlab.com>

doc/architecture/blueprints/cells/cells-feature-dashboard.md → doc/architecture/blueprints/cells/cells-feature-your-work.md

 ---
 stage: enablement
 group: Tenant Scale
-description: 'Cells: Dashboard'
+description: 'Cells: Your Work'
 ---
 
 <!-- vale gitlab.FutureTense = NO -->
@@ -13,18 +13,46 @@ contrast this with alternatives before deciding which approach to implement.
 This documentation will be kept even if we decide not to implement this so that
 we can document the reasons for not choosing this approach.
 
-# Cells: Dashboard
+# Cells: Your Work
 
-> TL;DR
+Your Work will be scoped to an Organization.
+Counts presented in the individual dashboards will relate to the selected Organization.
 
 ## 1. Definition
 
+When accessing `gitlab.com/dashboard/`, users can find a [focused view of items that they have access to](../../../tutorials/left_sidebar/index.md#use-a-more-focused-view).
+This overview contains dashboards relating to:
+
+- Projects
+- Groups
+- Issues
+- Merge requests
+- To-Do list
+- Milestones
+- Snippets
+- Activity
+- Workspaces
+- Environments
+- Operations
+- Security
+
 ## 2. Data flow
 
 ## 3. Proposal
 
+Your Work will be scoped to an Organization, giving the user an overview of all the items they can access in the Organization they are currently viewing.
+
+- Issue, Merge request and To-Do list counts will refer to the selected Organization.
+
 ## 4. Evaluation
 
+Scoping Your Work to an Organization makes sense in the context of the [proposed Organization navigation](https://gitlab.com/gitlab-org/gitlab/-/issues/417778).
+Considering that [we expect most users to work in a single Organization](../organization/index.md#data-exploration), we deem this impact acceptable.
+
 ## 4.1. Pros
 
+- Viewing Your Work scoped to an Organization allows Users to focus on content that is most relevant to their currently selected Organization.
+
 ## 4.2. Cons
+
+- Users working across multiple Organizations will have to navigate to each Organization to access all of their work items.

doc/architecture/blueprints/cells/index.md

@@ -321,7 +321,6 @@ This is the list of known affected features with proposed solutions.
 - [Cells: CI Runners](cells-feature-ci-runners.md)
 - [Cells: Container Registry](cells-feature-container-registry.md)
 - [Cells: Contributions: Forks](cells-feature-contributions-forks.md)
-- [Cells: Dashboard: Projects, Todos, Issues, Merge Requests, Activity, ...](cells-feature-dashboard.md)
 - [Cells: Database Sequences](cells-feature-database-sequences.md)
 - [Cells: Data Migration](cells-feature-data-migration.md)
 - [Cells: Explore](cells-feature-explore.md)
@@ -337,6 +336,7 @@ This is the list of known affected features with proposed solutions.
 - [Cells: Snippets](cells-feature-snippets.md)
 - [Cells: Uploads](cells-feature-uploads.md)
 - [Cells: User Profile](cells-feature-user-profile.md)
+- [Cells: Your Work](cells-feature-your-work.md)
 
 ## Frequently Asked Questions