Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • NFDI4Ing S-3
    Coscine
    External Project: NFDI4Ing S-3
  • NFDI4Ing S-4
    Coscine
    External Project: NFDI4Ing S-4
  • NFDI4Ing S-5
    Coscine
    External Project: NFDI4Ing S-5
  • NFDI-MatWerk
    Coscine
    External Project: NFDI-MatWerk
  • 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 related to the notification functionality in Coscine, such as implementing or improving notifications for events or fixing issues with existing notifications
  • Observers
    Coscine
    Should be used for issues or merge requests that include changes on Observers used in the API (Observer Pattern)
  • Should be used for issues or merge requests related to organizations or the Research Organization Registry (ROR) within Coscine
  • PIDs
    Coscine
    Should be used for issues or merge requests related to implementing or improving the functionality of persistent identifiers (PIDs) in Coscine
  • POBacklog 📋
    Coscine
    Marks an issue that has completed the refinement process and meets the Definition of Ready (DoR). This label indicates that the issue has been fully discussed, acceptance criteria are clearly defined, and it has been estimated appropriately. It is now prioritized in the backlog and ready for inclusion in a future sprint or development cycle.
  • Identifies an issue that requires further refinement before it can proceed. This label is used to earmark issues for discussion in the refinement meeting, where details will be clarified, acceptance criteria defined, and estimates given. Issues with this label are in preparation for being ready for development.
  • POReview
    Coscine
    This label signifies that the issue needs to be reviewed by the product owner or a designated team member. The review will assess the issue's validity, priority, and whether it aligns with the project's goals and current priorities. Following the review, the issue will be reclassified and assigned appropriate labels for further action.
  • POStale 🍂
    Coscine
    Labels an issue as stale. A stale issue has little to no value for the current and future state of the system and will be closed.
  • 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.
  • 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.
  • 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.
  • Project
    Coscine
    Should be used for issues or merge requests related to any topic about Projects in Coscine
  • 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
  • Quota
    Coscine
    Should be used for issues or merge requests related to managing quotas in Coscine, such as implementing or improving functionality
  • RDS.nrw
    Coscine
    External Project: RDS.nrw