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

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

Should be used for issues or merge requests related to improving the search functionality and overall discoverability in Coscine, such as implementing new search features or optimizing existing search algorithms

Should be used for issues or merge requests that are related to security and data protection topics, indicating that there are potential vulnerabilities or risks that need to be addressed

Should be used for issues that are currently being worked on by a developer, indicating that the issue has been claimed and is in progress

Should be used for issues or merge requests that have completed implementation and are currently being reviewed and tested by peer developers, indicating that the issue is in the peer-review testing phase