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 EPICs that are part of a larger initiative or project, and are ready for review by other team members or stakeholders
-
Should be used for EPICs that are part of a larger initiative or project, and are ideas or proposals that have not yet been fully fleshed out or added to the backlog
-
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
-
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 that have passed integration testing on the LIVE system and are currently in a functional state
-
Should be used for issues that have passed integration testing on the D-SP10 development system and are currently in a functional state
-
Should be used for issues or merge requests related to continuous integration and continuous deployment processes in the project, such as configuring CI/CD pipelines or fixing issues with existing pipelines
-
Should be used for issues that need to be prioritized and reviewed before they can be progressed
-
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 Users in Coscine
-
Should be used for issues or merge requests related to managing quotas in Coscine, such as implementing or improving functionality
-
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 any topic about Projects in Coscine
Prioritized