Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Should be used for issues or merge requests related to an issue reported over the Coscine's ServiceDesk email by an external user.
-
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 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 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 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 any topic about Resources 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 the form generator in Coscine and AIMS, such as implementing new features, improving performance, or addressing existing issues
-
Should be used for issues or merge requests related to Version 2 of Coscine's API, such as implementing new features, improving performance, or addressing issues with the API
-
Should be used for EPICs that are part of a larger initiative or project, and are currently being evaluated or prioritized for review
-
Should be used for EPICs that are part of a larger initiative or project, and have been completed and are no longer active
-
Should be used for EPICs that are part of a larger initiative or project, and are currently being worked on by the team
-
Should be used for EPICs that are part of a larger initiative or project, and have been added to the backlog for future consideration and planning
-
Should be used for EPICs that require further analysis or investigation before a solution or course of action can be determined, and are part of a larger initiative or project that requires coordination across multiple teams or features
Prioritized