FY22-Q3 Product OKR Planning: Adoption Through Usability

devopsverify

1. Deliver 5 or more "severity::2" issues in"FY22::Q3" related to ~security,~usability, and Compliance. => 100%

devopscreate

1. groupgitaly Increase adoption of Gitaly Cluster by completing Repository level incremental backups => 0%
2. groupgitaly Increase adoption of Gitaly Cluster by completing Add observability for Praefect database on GitLab.com => 0%
3. groupgitaly Increase adoption of Gitaly Cluster by completing Improve latency on Git access checks
4. groupgitaly Meet SLO for all P2/S2 bug ~performance (i.e. no issues are labeled as ~"missed-SLO") => 0%
5. groupgitaly Increase adoption of Gitaly Cluster by ensuring successful migration of 3 key accounts (as defined by CS & Sales) from NFS -Collaborate with Customer Success prior to the start of the quarter to identify the 3 key accounts => 0%
6. ~"group::editor" Increase number of commits created per month from the Web IDE from 800k to 1M by improving the MR <-> Web IDE workflow => 0%
7. ~"group::editor" Make the Content Editor the default Markdown Editing experience on Wiki by implementing full support of GitLab Flavored Markdown extensions => 0%
8. groupcode review Complete Better defined mergability => 0%
9. groupcode review Complete Merge Widget restructuring => 0%
10. groupsource code Complete migration of all X file type viewers to Repository Browser - X file types to be determined at end of current quarter once we assess progress => 0%

devopsplan

1. groupproduct planning Complete 40% of the issues for Viable maturity by converting current Requirement implementation to a shared Work Items implementation.
2. groupproject management From the start of development, decrease the work to release a new work item to gitlab.com by 50%.

devopspackage

1. ~"group::package" Increase adoption of the Package Registry user interface by increasing the number of page views by 12%. ✅ (100% complete)

---

This issue serves as a container to discuss and add product group KRs. Please add your Product group KRs above to this issue in the following format. If you do not yet have issues to link to, it's ok, they can be added as you create them at a later time. Details on the Q3 Product team KR planning can be found here.

SAMPLE

1. sectiondev: Implement items from the architectural blueprint for consolidating Groups and Projects into a single container (https://gitlab.com/gitlab-org/architecture/tasks/-/issues/7)
2. grouptesting: Move a low usage / paid feature to Core