This label signifies that the issue needs to be reviewed by the product owner or a designated team member. The review will assess the issue's validity, priority, and whether it aligns with the project's goals and current priorities. Following the review, the issue will be reclassified and assigned appropriate labels for further action.

Identifies an issue that requires further refinement before it can proceed. This label is used to earmark issues for discussion in the refinement meeting, where details will be clarified, acceptance criteria defined, and estimates given. Issues with this label are in preparation for being ready for development.

Marks an issue that has completed the refinement process and meets the Definition of Ready (DoR). This label indicates that the issue has been fully discussed, acceptance criteria are clearly defined, and it has been estimated appropriately. It is now prioritized in the backlog and ready for inclusion in a future sprint or development cycle.

Applicable to issues or merge requests involving the management, access, and security of sensitive data and configuration settings within the project. This includes tasks like setting up secret keys, configuring environment variables, or addressing concerns related to the secure handling and storage of credentials.

Should be used for issues or merge requests related to legal and compliance topics, the terms of service or privacy policy.

External Project: DataStorage.nrw