Labels

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.

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.

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.

Labels an issue as stale. A stale issue has little to no value for the current and future state of the system and will be closed.

Should be used for issues that are important and need to be addressed in a timely manner. Issues should be ideally addressed within a sprint or two.

Should be used for issues that are minor or low priority and can be addressed later. Issues may take several weeks or even months to be addressed and the team may have other more pressing issues to address first.

Should be used for issues that are important but not as urgent as high priority issues. Issues may take a few weeks to be addressed, depending on the team's workload and priorities.

Should be used for issues or merge requests related to any topic about Projects in Coscine

Should be used for issues related to Quality of Life improvements, such as refactoring, cleaning up, or other improvements that are not directly related to adding new features or fixing bugs

Should be used for issues or merge requests related to managing quotas in Coscine, such as implementing or improving functionality

External Project: RDS.nrw

Should be used for issues that have been closed and have all their related projects merged into their respective default branch (master/main)

Should be used for issues or merge requests related to any topic about Resources in Coscine

Should be used for issues or merge requests related to any topic about Resource Types in Coscine

Should be used for issues or merge requests that require conceptualization or brainstorming around a particular workflow or feature. Remove the label once done.

Should be used for issues that need to be prioritized and reviewed before they can be progressed

Should be used for issues or merge requests that require a detailed technical review, architecture, or design of a feature. Remove the label once done.

Should be used for issues or merge requests related to managing user roles and permissions, as well as enforcing access control and ensuring compliance with data protection regulations in Coscine

Epics / Issues that realize stakeholder demands from the RWTH

Should be used for issues or merge requests that require the execution of a script on a specific system