Labels

Improvement or feature to be implemented in a SecAuto product or a supporting component initiated by an external team

Outages and related fire-fighting related to products and tooling by SecAuto

Work on non-product-related tooling internal to the Security Automation team

Recurring or one-off work required to keep our products operative and usable

Signals that an issue and discussions contained therein are related to the management of the SecAuto team and ancillary topics

Signals that the SecAuto team is working on a task but is waiting for input from the customer.

Signals that a work unit and associated results require joint review by the SecAuto manager

Signals that a work unit and associated results require review by SecAuto team

Signals that a work unit cannot be brought forward by SecAuto due to one or multiple blockers

Signals that a work unit is no longer desired and hence shall not be delivered by SecAuto

Signals that a work unit has been both delivered by SecAuto and accepted by the final customer

Signals that a work unit is in-progress and to be delivered by SecAuto

Signals that this is a new potential task for the SecAuto team to triage, prioritize and if accepted execute on

Signals that a work unit has been triaged, properly scoped and is ready to be worked on by SecAuto

Issues that are blocked and need a resolution plan or escalation. Move to ~"seccomp workflow::in progress" or ~"seccomp workflow::ready" once unblocked.

Issue closed because the work was cancelled because it was no longer needed or relevant.

Issue closed because work is completed as described.

Issues that are being actively worked by the team and should have a health status and an assignee. Stale issues with this label should be moved to blocked or cancelled.

An idea or opinion on how to proceed. It's been triaged/scoped but not yet considered "ready".