Should be used for issues or merge requests related to the login functionality of Coscine, such as implementing or improving the login process

Should be used for issues or merge requests related to managing metadata in Coscine

Should be used for issues or merge requests that include changes on Middlewares used in the API

External Project: NFDI4Ing S-2

External Project: NFDI4Ing S-3

External Project: NFDI4Ing S-4

External Project: NFDI4Ing S-5

External Project: NFDI-MatWerk

Should be used for cases, where an issues is purely constrained to our process and/or pipelines, but is detached from Coscine as a service, thus no deployment of any kind is possible

Should be used for issues or merge requests related to the notification functionality in Coscine, such as implementing or improving notifications for events or fixing issues with existing notifications

Should be used for issues or merge requests that include changes on Observers used in the API (Observer Pattern)

Should be used for issues or merge requests related to organizations or the Research Organization Registry (ROR) within Coscine

Should be used for issues or merge requests related to implementing or improving the functionality of persistent identifiers (PIDs) in Coscine

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.