Labels

Use this for epics that include FY27-Q3 work, even if they span multiple quarters.

use this label if you have want the epic to be part of Q3 planning

Use this label if the epic had FY27-Q3-CANDIDATE label and now its deferred to later quarter than Q3

Use this for epics that include FY27-Q4 work, even if they span multiple quarters.

use this label if you have want the epic to be part of Q4 planning

Use this label if the epic had FY27-Q4-CANDIDATE label and now its deferred to later quarter than Q4

Feb-Apr of 2026

May-Jul of 2026

Aug-Oct of 2026

Oct 2026 to Jan 2027

Version of the feature working towards or related to based on https://docs.gitlab.com/development/documentation/experiment_beta/

Version of the feature working towards or related to based on https://docs.gitlab.com/development/documentation/experiment_beta/

Version of the feature working towards or related to based on https://docs.gitlab.com/development/documentation/experiment_beta/

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

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**

Next step: clarification or information from Compliance

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

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

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.