giseldo/neodataset huggingface dataset:
SIRT Incidents PI changes

Seems like we have multiple PIs/KPIs around SIRT incidents:

- Security Engineer On-Call Page Volume (Security Incidents that required paging someone)
- Security Incidents by Category
- ~~Security Incidents by Impacted Organization~~

I propose we keep the KPI, remove the other as PI, & move all these charts to new "Security Incidents" standalone dashboard to provide this detail.

Question: Do we really need these to be standalone PIs, or do we just want to be able to see them readily?

Story points: 5.0
Security Control Health KPI

Any way we can track this data over time & have it in Sisense/ data warehouse? Is this tracked in a spreadsheet somewhere?

Current KPI: https://about.gitlab.com/handbook/engineering/security/performance-indicators/#security-control-health

Examples for redesign: https://docs.google.com/spreadsheets/d/1_-Bm_vVLPNts1xmshNjH2NDN3GjLPxJGyBreh0uqQYk/edit?usp=sharing

Story points: 1.0
Security Engineer On-Call Page Volume KPI change

- [ ] 
 add target (consider making target logic simpler, maybe just 50% over avg of last 12 months)
 No target because it's a stacked bar chart.
- [ ] 
 add Sisense chart embed if not confidential, otherwise note confidential 
 This is mentioned in the KPI description `For Security purposes, please view this chart directly in Sisense.`
- [X] kpi definition mentions severity, anything we should consider about differing severity for this KPI?
- [x] match KPI naming with chart name in Sisense


https://about.gitlab.com/handbook/engineering/security/performance-indicators/#security-engineer-on-call-page-volume

https://app.periscopedata.com/app/gitlab/592612/Security-KPIs?widget=9217413&udv=0

Story points: 3.0
Avg Age of Vulnerability KPI change

- [x] Change Avg Age of Vulnerability to match OBA logic https://about.gitlab.com/handbook/engineering/quality/performance-indicators/#s1-oba
  - [x] Alternatively, if mainly want to track towards SLO, consider changing to # open vulnerabilities past SLO (similar to corrective actions past SLO)
- [x] if metric needs to be confidential add confidential note, if not add sisensechart embed

Story points: 3.0
Pricing page code cleanup v1

## Before creating an issue

- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

- https://about.gitlab.com/pricing/

## What does the request INCLUDE?

#### Insert the request here:
- Remove unused code/experiments

Story points: 1.0
Incorporate GItLab Incident Severities into issues dbt model

Once `issuable_severities` base model is in dbt, need to use that severity field in main `issues_xf` model to bring that in.

Logic will basically look like a CASE statement where it pulls from `issuable_severities` severity field first if they exist, & if not then tried to use current label method. That should bring in severities for both GitLab Incidents & GitLab Issues in same model

Story points: 3.0
add issuable_severities table to Data warehouse

As part of https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/11978 we need to bring a new table `issuable_severities` into the data warehouse to get the right severity values for GitLab Incidents


- [x] add to manifest 
- [x] create source tables
- [x] create base model

Story points: 5.0
Pricing page updates

## Before creating an issue

- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

- https://about.gitlab.com/pricing/

## What does the request INCLUDE?

#### Insert the request here:
- Change "FREE" to "Free" on mobile.
- Remove brackets around text.
- Add clarity that CI/CD minutes are for SaaS Only (tooltips, content changes).

Story points: 1.0
Rename Vacancy Time to Fill KPI

From Eric's feedback in https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84142#note_614685642, rename Vacancy Time to Fill KPI to "Average Age of Open Vacancies"

- [ ] Renamed Metric for `Engineering Division` https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85641
- [ ] Renamed Metric for ~"Customer Support Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85639
- [ ] Renamed Metric for ~"Development Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85637
- [ ] Renamed Metric for ~"Infrastructure Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85252
- [ ] Renamed Metric for ~"Quality Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85826
- [ ] Renamed Metric for ~"UX Department"  https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85827
- [ ] Renamed Metric for ~"Security Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85830

Story points: 1.0
Ensure all KPI charts/dashboards are set to auto refresh

Ensure all KPI charts/dashboards are set to auto-refresh for monthly key/group conversations. Open a separate data team issue.

Engineering Division
1. https://app.periscopedata.com/app/gitlab/620621/Engineering-Handbook-MR-Rate
2. https://app.periscopedata.com/app/gitlab/686926/Engineering-Division-MR-Rate
3. https://app.periscopedata.com/app/gitlab/842240/Engineering-Division-New-Hire-Location-Factor-Shared-Dashboard
4. https://app.periscopedata.com/app/gitlab/864877/Team-Member-Retention-Dashboard
5. https://app.periscopedata.com/app/gitlab/872394/Average-Age-of-Open-Positions

Development Department
1. https://app.periscopedata.com/app/gitlab/899982/InfraDev
2. https://app.periscopedata.com/app/gitlab/761256/Largest-Contentful-Paint-at-P90
3. https://app.periscopedata.com/app/gitlab/705845/Renewal-Customer-Satisfaction
4. https://app.periscopedata.com/app/gitlab/862325/Development-Department-Retention
5. https://app.periscopedata.com/app/gitlab/929641/Development-Department-Average-Age-of-Open-Positions
6. https://app.periscopedata.com/app/gitlab/871128/Open-MR-Review-Time-(OMRT)

Quality Department
1. https://app.periscopedata.com/app/gitlab/516343/Quality-Department-KPIs
2. https://app.periscopedata.com/app/gitlab/862331/Quality-Department-Retention
3. https://app.periscopedata.com/app/gitlab/856737/S1-Open-Bug-Age-(OBA)
4. https://app.periscopedata.com/app/gitlab/856747/S2-Open-Bug-Age-(OBA)
5. https://app.periscopedata.com/app/gitlab/878780/Time-to-first-failure-(TtFF)
6. https://app.periscopedata.com/app/gitlab/872455/Open-Community-MR-Age-(OCMA)

UX Department
1. https://app.periscopedata.com/app/gitlab/462325/UX-KPIs
2. https://app.periscopedata.com/app/gitlab/882285/Product-Design-MRs
3. https://app.periscopedata.com/app/gitlab/862334/UX-Department-Retention

Security Department
1. https://app.periscopedata.com/app/gitlab/641782/Appsec-KPIs
2. https://app.periscopedata.com/app/gitlab/592612/Security-KPIs
3. https://app.periscopedata.com/app/gitlab/847984/ZenGRC-Point-in-Time-Screenshots-(Interim-Dashboard)
4. https://app.periscopedata.com/app/gitlab/780726/WIP:-Blocked-User-Usage-Data
5. https://app.periscopedata.com/app/gitlab/862338/Security-Department-Retention

Support Department
1. https://app.periscopedata.com/app/gitlab/463858/Engineering-KPIs
2. https://app.periscopedata.com/app/gitlab/855241/Customer-Wait-Time-Ratio
3. https://app.periscopedata.com/app/gitlab/862336/Support-Department-Retention
4. https://app.periscopedata.com/app/gitlab/686943/Support-Department-MR-Rate
5. https://app.periscopedata.com/app/gitlab/621060/Support-Handbook-MR-Rate

Incubation Department
1. https://app.periscopedata.com/app/gitlab/908949/Incubation-Engineering-Department-MR-Rate

Story points: 3.0
Create a "Confidential" Health state for PIs

## Summary

With a increasing emphasis on correctly maintaining confidential information many of the Infrastructure PIs no longer indicate [health status](https://0623-sloyd-infra-pi.about.gitlab-review.app/handbook/engineering/infrastructure/performance-indicators/#health), but by doing so the status defaults to "Unknown".

![image](/uploads/22df651aeea4b8ab7bf3d4d4875bee71/image.png)

This is confusing though as there is a difference between what we really intend when we show status Unknown vs. when it is actually known but just can't be displayed due to confidentiality.

## Proposal
- Create a "Confidential" Health status with appropriate icon...(maybe transparent background with black text so as not to imply anything via other coloring?)
- Update the Health legend in the template for all PIs
- Review all Eng department PIs for those which should switch to use the new status

## Actions
- [ ] Discuss among Engineering Data Analytics and Eng Dept heads to validate the problem.
- [ ] Eng Data Analytics represents the proposal to other Divisions
- [ ] Implement above proposal (or the iteration we arrive at)

Story points: 3.0
Ensure we capture the next steps for PIs with health attention and problem

From the recent Key Reviews,

> For the items that are noted as a problem or attention, can you include get well plan, actions taken from the last meeting and lessons learned.  If it helps, I could provide a template for this.  Thanks. Purpose is that a lot of people on the call can learn from what y’all are doing.

From feedback in my 1-1 factoring this in the the structure would be overkill. The suggestion would be to remind folks to capture next steps in the bullets.

Story points: 1.0
Update middleman to avoid reference through git ref

With !78850 (#10917, gitlab-org&5149) and !73459, we introduced the Git ref to use middleman gem with Ruby 2.7/3.0 support, but the upstream just released 4.4.0 (2021-06-16), so it is time to switch back to the official release.

- https://github.com/middleman/middleman/releases/tag/v4.4.0
- https://rubygems.org/gems/middleman/versions/4.4.0

Story points: 4.0
OBA S1 S2 Polishes

* Please make this 2 years - I want to set OBA S1 to green since we improved alot from 2 years ago. When it is 1 year the context is lost.
  * https://about.gitlab.com/handbook/engineering/quality/performance-indicators/#s1-open-bug-age-oba 
  * https://about.gitlab.com/handbook/engineering/quality/performance-indicators/#s2-open-bug-age-oba 
* Also the number of outstanding issue is mismatched between OBA S1 and Average Age
https://app.periscopedata.com/shared/ae618b53-194d-40ed-a3ca-7f0d4ca9a492? 

| Previous | Current |
| ------ | ------ |
| ![Screen_Shot_2021-06-17_at_12.51.42_PM](/uploads/2f513a551608777a529f0b980b34ae6e/Screen_Shot_2021-06-17_at_12.51.42_PM.png) | ![Screen_Shot_2021-06-17_at_12.51.38_PM](/uploads/d95cc62393903971bf9dce7640fece1b/Screen_Shot_2021-06-17_at_12.51.38_PM.png) |

Story points: 2.0
Non headcount budget PI is stale

From UX Key Review, we discovered that the non-headcount budget PI is stale. Clarify broadly for all PIs

## Tasks
* Data is in Adaptive hence all charts are stale
* This data is confidential hence directed to Sisense for `target`
* Set `health` to unknown
* Link tracking issue in PI description https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/11464
* Addresses https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/11970

## MRs
* Engineering https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85248
* ~"UX Department"  https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84607
* ~"Quality Department"  https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85245
* ~"Development Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85249
* ~"Security Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85253
* ~"Customer Support Department" (dashboard deleted) https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85251
* ~"Infrastructure Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85252

cc @gl-quality/eng-analytics

Story points: 1.0
Standardize all KPI's current month's bar to have a different color

- From June 2021 UX Key review Purple bar for TW MR Rate for current month
- This helps reduce back/forth between stakeholders, not having this differentiation leads to a false sense of urgency when we don't have all the data for the current month
- We have a guideline to have this as optional https://about.gitlab.com/handbook/engineering/metrics/#guidelines. 


## Proposal
- Standardize green bar for current month for all KPIs

| Current | Desired |
| ------ | ------ |
| ![Screen_Shot_2021-06-17_at_12.25.52_PM](/uploads/cdb6ee9341f199f1ac0f9fc9cfba4733/Screen_Shot_2021-06-17_at_12.25.52_PM.png) | ![Screen_Shot_2021-06-17_at_12.25.25_PM](/uploads/dde878f0328497bbc484ed533087ff80/Screen_Shot_2021-06-17_at_12.25.25_PM.png) |


### Challenges
- Team implements this via 2 code sections and is the equivalent of creating 2 charts into 1.
- Explore helpers 
  - Is there a visualization library that we can plug in ? do it at the visualization level and not the calculation.
  - render API ? for “color” gives no result, so not looking promising
  - ask Sisense what’s possible in terms of styling that doesn’t muddy up business logic?

### Completion
- [x] Completed for `Engineering Division` KPIs @lmai1 
- [x] Completed for `Engineering Division` PIs @lmai1 
- [X] Completed for ~"Customer Support Department" KPIs @lmai1 
- [X] Completed for ~"Customer Support Department" PIs @lmai1 
- [x] Completed for ~"Development Department" KPIs @lmai1 
- [x] Completed for ~"Development Department" PIs @lmai1 
- [x] Completed for ~"Infrastructure Department" KPIs @davis_townsend 
  - Availability fix being tracked in https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/11910
- [x] Completed for ~"Quality Department" KPIs @davis_townsend 
- [X] Completed for ~"Quality Department" PIs @lmai1 
- [x] Completed for ~"Security Department" KPIs @davis_townsend 
- [X] Completed for ~"UX Department" KPIs @lmai1
- [X] Completed for ~"UX Department" PIs @lmai1

Story points: 8.0
Deprecate Hiring Actuals v Plan

After https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/11418 is closed, we should be able to deprecate hiring actuals v plan metric for all eng departments

- [ ] Removed Metric for `Engineering Division` https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85641
- [ ] Removed Metric for ~"Customer Support Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85639
- [ ] Removed Metric for ~"Development Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85637
- [ ] Removed Metric for ~"Infrastructure Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85252
- [ ] Removed Metric for ~"Quality Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85826
- [ ] Removed Metric for ~"UX Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85636
- [ ] Removed Metric for ~"Security Department" https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/85635

Story points: 1.0
Promote Retention to KPI for all departments

From weekly team meeting today, as per Eric's feedback we should promote the recently introduced Retention Metric to KPI for each department along with Time to Fill Vacancies

- [x] Completed for `Engineering Division`
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84142
- [x] Completed for ~"Customer Support Department"
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84127
- [x] Completed for ~"Development Department"
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84129
- [x] Completed for ~"Infrastructure Department"
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/83163
- [x] Completed for ~"Quality Department"
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84131
- [x] Completed for ~"Security Department"
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84134
- [x] Completed for ~"UX Department"
  - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84133

Story points: 1.0
Cookie consent script adjustments

Per the related Marketing Ops issue, https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/5018#note_595713842, we need to adjust the javascript responsible for OneTrust to load sooner.

I plan to move this logic into the same spot as the cookiebot logic in the includes/layout/head file.

This shouldn't negatively impact anything, but since we can only test it on production, it's theoretically possible to break cookiebot or accidentally introduce OneTrust to unexpected pages.

I shall carefully monitor the deployment and follow up with regression tests.

Story points: 1.0
Have the 'Knowledge_Design_Collection' route LCP under 4s

[The route's dashboard.](https://dashboards.gitlab.net/d/000000043/sitespeed-page-summary?orgId=1&var-base=sitespeed_io&var-path=desktop&var-testname=gitlab&var-group=gitlab_com&var-page=Knowledge_Design_Collection&var-browser=chrome&var-connectivity=cable&var-function=median&var-resulturl=https:%2F%2Fs3.amazonaws.com%2Fresults.sitespeed.io&var-screenshottype=jpg)

The current LCP metrics at the time of the issue's creation:

![Screenshot_2021-06-07_at_10.41.21](/uploads/ac945074e48b6cd9fc3958687074d0ad/Screenshot_2021-06-07_at_10.41.21.png)

We should aim at moving the LCP down to under 4 seconds at minimum. Moving it below 2.5s is the ultimate goal but is not essential for this issue.

Story points: 2.0
GitLab.com Availability - display 2 decimal points in chart mouseover

## Problem
The chart for [GitLab.com Availability](https://0603infra-pi.about.gitlab-review.app/handbook/engineering/infrastructure/performance-indicators/#gitlabcom-availability) displays only 1 decimal point in the mouseover display, which is insufficient detail for a metric such as availability.

![image](/uploads/8c426767e3bfb8574c48f47e287821d9/image.png)

## Expected Outcome
Figure out how to display at 2 decimal points, or validate that this isn't possible...in which case we need to open (or escalate) a product request with Sisense.

Story points: 5.0
Broken links on /continuous-delivery/

## Before creating an issue

- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

- https://about.gitlab.com/stages-devops-lifecycle/continuous-delivery/
## What does the request INCLUDE?

#### Insert the request here:
- 2 Broken links under "What is GitLab continuous delivery?"
- 1 Broken link under "Multicloud deployment"

Story points: 1.0
Minor Pricing page updates

## Before creating an issue

- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

- https://about.gitlab.com/pricing/

## What does the request INCLUDE?

#### Insert the request here:
- Free-forever features for individual users
- Enhance your team productivity and coordination
- Organization wide security, compliance, and planning
- Remove Free-forever features bullet
- Remove "Get" before each of the CI minutes
- Free static websites => Static websites
- Remove [1] after No credit card required (keep it for 400 CI minutes)

Story points: 1.0
Pricing page minor updates

## Before creating an issue

- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

- https://about.gitlab.com/pricing/

## What does the request INCLUDE?

#### Insert the request here:

Per Slack feedback from Sid,

- The 'Get x,0000 CI/CD minutes per month' items should have a bullet in front, not a + (don't expand it, remove the percent comparison)
    - Engineer's note: This was updated on both the control and test variants.
- The text 'Buy Premium for DevOps' and 'Buy Ultimate for DevOps' doesn't make sense to me, I suggest saying 'Buy GitLab Premium' and 'Buy GitLab Ultimate'.
    - Engineer's note: I did this on only the test variant. I did not update the control variant at this time.

Story points: 1.0
Follow-up from "Add inline_svg extension and leverage in heading component for event template"

The following discussion from !82454 should be addressed:

- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/82454#note_583828959):  (+5 comments)

    > I think this is a great extension that will enable the Digital Experience team to implement a Slippers `svg` icon library in the repo and utilize it efficiently in our templates. 
    > 
    > WDYT @brandon_lyon @tywilliams

Story points: 1.0