Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 90
⏳ Script Execution Pending
Coscine
Should be used for issues or merge requests that require the execution of a script on a specific system
Testing Limitations ❕
Coscine
Should be used for issues or merge requests that are complete but have limitations on testing due to access or permission issues that can only be resolved by a user with the appropriate permissions
Tested on D-SP10 ✔
Coscine
Should be used for issues that have passed integration testing on the D-SP10 development system and are currently in a functional state
Tested on LIVE ✔
Coscine
Should be used for issues or merge requests that have passed integration testing on the LIVE system and are currently in a functional state
Deployed to LIVE ✔
Coscine
Should be used for issues that have been closed and have all their related projects deployed in their latest version to the LIVE system
Deployed to D-SP10 ✔
Coscine
Should be used for issues that have been closed and have all their related projects deployed in their latest version to the D-SP10 development system
PrioMedium
Coscine
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.
PrioLow
Coscine
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.
PrioHigh
Coscine
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.
Feature Request
Coscine
Should be used for issues related to a new feature or functionality that needs to be added and has been requested by stakeholders of the project
ReviewPrioritization
Coscine
Should be used for issues that need to be prioritized and reviewed before they can be progressed
QoL
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
Resource Types
Coscine
Should be used for issues or merge requests related to any topic about Resource Types in Coscine
Resources
Coscine
Should be used for issues or merge requests related to any topic about Resources in Coscine
Users
Coscine
Should be used for issues or merge requests related to any topic about Users in Coscine
Project
Coscine
Should be used for issues or merge requests related to any topic about Projects in Coscine
Quota
Coscine
Should be used for issues or merge requests related to managing quotas in Coscine, such as implementing or improving functionality
Metadata
Coscine
Should be used for issues or merge requests related to managing metadata in Coscine
Organizations & RORs
Coscine
Should be used for issues or merge requests related to organizations or the Research Organization Registry (ROR) within Coscine
No Deployment 🔹
Coscine
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