Batching suggested changes to HHQ requirements

What problem(s) will it solve?

Far KSAT's which are driven by higher headquarters requirements documents (JCT&CS, ACC CDD, etc.) we need a way to batch up the issues (change, add, removals) so when those change windows open (annually, etc.) we are able to raise them and get them changed.

For example, if someone wants to change a CFETP 3D0X4 KSAT they would need to work with the STRT process.

Who is the intended user(s)?

Anyone with a desire to change a HHQ KSAT - Wants to understand when/how their issue will be resolvable. HHQ requirements owners - will want a way to see which changes are being proposed.

Lay out the expected user experience

A user identifies a KSAT requires work and opens an issue.
Upon submission we identify that the KSAT affected is owned by a HHQ entity.
(Problem to be solved) The issue needs to be organized (e.g. Milestone, Label, etc.) to align it with that source document.
A response is crafted to the submitted saying when the KSAT may be able to be changed
Upon the change window for the source document we take all batched issues and submit them to the OPR.
OPR accepts, rejecs the change and issues a new source document.
MTTL is updated to reflect new source document.
Original issue is closed.

Proposal

Option 1: Use labels to aligned Issue/KSAT to requirements documents. (e.g. JCT&CS, etc.)

*Option 2: Use a milestone to align issue/ksat to requirements documents

Option 3:

Further details

Each requirement document might have different rules, details, OPR's, etc. so adopting changes will vary between sources.
Sources will be potentially extremely varied. We can have flight level sources, squadron level sources, issue level sources, grp/wg/naf level sources, etc.

Permissions and Security

Labeling and assigning issues to milestones should be available to all personnel with at least developer rights.

Documentation

Write an article detailing the triage and handling procedures for tickets relating to changes to KSAT's out of our control.
Add handling procedures to CYT training specialization.

Availability & Testing

Tabletop reception of tickets and our handling

What does success look like, and how can we measure that?

We are able to handel requests to change KSAT's driven by source documents more effectively.