Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.

Labels

  • Logging
    Should be used for issues or merge requests related to logging functionality in Coscine, such as implementing or improving logging features
    Coscine
  • Login
    Should be used for issues or merge requests related to the login functionality of Coscine, such as implementing or improving the login process
    Coscine
  • Metadata
    Should be used for issues or merge requests related to managing metadata in Coscine
    Coscine
  • MoSCoWCo
    Coscine
  • MoSCoWMo
    Coscine
  • MoSCoWS
    Coscine
  • MoSCoWWo
    Coscine
  • NFDI4Ing Base
    External Project: NFDI4Ing Base Services
    Coscine
  • NFDI4Ing S-2
    External Project: NFDI4Ing S-2
    Coscine
  • NFDI4Ing S-3
    External Project: NFDI4Ing S-3
    Coscine
  • NFDI4Ing S-4
    External Project: NFDI4Ing S-4
    Coscine
  • NFDI4Ing S-5
    External Project: NFDI4Ing S-5
    Coscine
  • NFDI-MatWerk
    External Project: NFDI-MatWerk
    Coscine
  • No Deployment 🔹
    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
    Coscine
  • Notification System
    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
    Coscine
  • Organizations & RORs
    Should be used for issues or merge requests related to organizations or the Research Organization Registry (ROR) within Coscine
    Coscine
  • Pending Closure ♻️
    Should be used for issues or merge requests that are no longer needed and will be closed in the near future
    Coscine
  • PIDs
    Should be used for issues or merge requests related to implementing or improving the functionality of persistent identifiers (PIDs) in Coscine
    Coscine
  • PrioHigh
    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.
    Coscine
  • PrioLow
    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.
    Coscine