Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • NFDI4Ing S-5
    Coscine
    External Project: NFDI4Ing S-5
  • NFDI-MatWerk
    Coscine
    External Project: NFDI-MatWerk
  • EPICIdea Tank
    Coscine
    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
  • VVM
    Coscine
    External Project: V&V Methoden
  • EPICFunnel
    Coscine
    Should be used for EPICs that are part of a larger initiative or project, and are currently being evaluated or prioritized for review
  • Form Generator
    Coscine
    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
  • PIDs
    Coscine
    Should be used for issues or merge requests related to implementing or improving the functionality of persistent identifiers (PIDs) in Coscine
  • ReviewTechnical
    Coscine
    Should be used for issues or merge requests that require a detailed technical review, architecture, or design of a feature. Remove the label once done.
  • ReviewConcept
    Coscine
    Should be used for issues or merge requests that require conceptualization or brainstorming around a particular workflow or feature. Remove the label once done.
  • 🔥
    Coscine
    Should be used for issues or merge requests that require immediate deployment to LIVE once they are completed, indicating the urgency of the task
  • Should be used for issues or merge requests that are related to security and data protection topics, indicating that there are potential vulnerabilities or risks that need to be addressed
  • RDS.nrw
    Coscine
    External Project: RDS.nrw
  • Status: Doing
    Coscine
    Should be used for issues that are currently being worked on by a developer, indicating that the issue has been claimed and is in progress
  • Should be used for issues or merge requests that have completed implementation and are currently being reviewed and tested by peer developers, indicating that the issue is in the peer-review testing phase
  • Bug
    Coscine
    Should be used for issues or merge requests that describe a bug or unexpected behavior in Coscine that needs to be fixed
  • Released ✔
    Coscine
    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 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 organizations or the Research Organization Registry (ROR) within Coscine
  • Metadata
    Coscine
    Should be used for issues or merge requests related to managing metadata in Coscine
  • Quota
    Coscine
    Should be used for issues or merge requests related to managing quotas in Coscine, such as implementing or improving functionality