Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • 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
  • Should be used for issues that have been closed and have all their related projects deployed in their latest version to the LIVE system
  • Feature Request
    Coscine
    Should be used for issues related to a new feature or functionality that needs to be added and has been requested by stakeholders of the project
  • Metadata
    Coscine
    Should be used for issues or merge requests related to managing metadata in Coscine
  • PIDs
    Coscine
    Should be used for issues or merge requests related to implementing or improving the functionality of persistent identifiers (PIDs) in Coscine
  • Rights & Roles
    Coscine
    Should be used for issues or merge requests related to managing user roles and permissions, as well as enforcing access control and ensuring compliance with data protection regulations in Coscine
  • UI & UX
    Coscine
    Should be used for issues or merge requests related to user interface (UI) and user experience (UX) design in Coscine, such as implementing new UI elements, improving existing designs, or addressing usability issues
  • Logging
    Coscine
    Should be used for issues or merge requests related to logging functionality in Coscine, such as implementing or improving logging features
  • Should be used for issues or merge requests related to improving the search functionality and overall discoverability in Coscine, such as implementing new search features or optimizing existing search algorithms
  • Should be used for issues or merge requests that require immediate attention, indicating that there is a significant problem that needs to be resolved
  • Should be used for issues or merge requests related to organizations or the Research Organization Registry (ROR) within Coscine
  • Should be used for issues or merge requests related to tracking key performance indicators (KPIs) and generating reports for Coscine
  • Waiting
    Coscine
    Should be used for issues or merge requests that are waiting for further input or action from another team member, such as waiting for a review or feedback
  • 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.
  • 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
  • Should be used for issues that have been closed and have all their related projects deployed in their latest version to the D-SP10 development system
  • Resource Types
    Coscine
    Should be used for issues or merge requests related to any topic about Resource Types in Coscine