Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • Should be used for issues or merge requests related to legal and compliance topics, the terms of service or privacy policy.
  • IAM4NFDI
    Coscine
    Identity Management Project from NFDI4Base Services
  • Applicable to issues or merge requests involving the management, access, and security of sensitive data and configuration settings within the project. This includes tasks like setting up secret keys, configuring environment variables, or addressing concerns related to the secure handling and storage of credentials.
  • 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.
  • Templating
    Coscine
    Should be used for issues or merge requests for new implementation of templates or the changing or updating of existing ones.
  • Trees
    Coscine
    Should be used for issues or merge requests that require changes on the topic of metadata and file trees (as reference to the old Tree API)
  • Middleware
    Coscine
    Should be used for issues or merge requests that include changes on Middlewares used in the API
  • Error Handling
    Coscine
    Should be used for issues or merge requests that refer to improper error handling (e.g. thrown 500 errors, that are not properly captured)
  • Endpoints
    Coscine
    Should be used for issues or merge requests related to updating or adding endpoints inside the Coscine's API
  • CRON
    Coscine
    Should be used for issues or merge requests that touch on the topic of scheduling specific scripts and tasks of repetitive nature
  • Blobs
    Coscine
    Should be used for issues or merge requests that require changes on the topic of file blobs and file objects (as reference to the old Blob API)
  • Should be used for issues or merge requests that touch on the topic of application profiles, their definition, labelling, processing or deployment
  • Certificate
    Coscine
    Should be used for issues or merge requests related to certificates
  • Observers
    Coscine
    Should be used for issues or merge requests that include changes on Observers used in the API (Observer Pattern)
  • API
    Coscine
    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