The UX Researcher is consulted on specific aspects of a study. Product/Design is drives project management aspects of execution and completing most tasks, with advice from a UX Researcher. The team tags the UX Researcher in the issue to provide context and a due date for when feedback is needed.

The UX Researcher takes on specified tasks within a study and advises on the rest. Product and Design drive project management aspects of execution and completing most tasks with support from the UX Researcher.

For documentation updates or additions that originate from a Customer Success knowledge base issue (solutions architecture).

Next step: product group or subject matter expert reviews issue and identifies next steps

Next step: FedRAMP Product Manager updates, reviews, moves, or closes this issue

Next step: clarification or information from Compliance

Required for Readiness Assessment (our first compliance assessment). **Do not remove this label without coordinating with FedRAMP PM and Compliance. Questions: #wg_fedramp**

FedRAMP PM and Compliance have determined this issue is not required to satisfy FedRAMP controls. (It may be needed for other reasons.) Only FedRAMP PM or Compliance should apply this label.

Next step: implement the change. This indicates that no further FedRAMP control analysis is currently required.

Needs to be complete for Security Assessment. See timeline in https://internal-handbook.gitlab.io/handbook/engineering/fedramp-compliance/#key-milestones. **Do not remove this label without coordinating with FedRAMP PM and Compliance. Questions: #wg_fedramp**

Large, strategic, rigorous projects that could benefit from a research specialist. Typically, foundational research, complex research questions, or high-priority problem validation.

Data Partitioning effort in support of implementing the CI/CD Time Decay blueprint - https://docs.gitlab.com/ee/architecture/blueprints/ci_data_decay/

SaaS services for the US Public Sector

SaaS services for the US Public Sector

All issues and MRs related to the Infrastructure Cost Data category within group::scalability. https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability/

A follow-up, action or next step following a group retrospective

This label keeps track of Community contribution MRs where author have been reminded to take action on their MR