Skip to content

Prioritized labels 0

Drag to reorder prioritized labels and change their relative priority.

Other labels 19

  • All issues related to any corelink client should be tagged with this
  • All issues related to any corelink client should be tagged with this
  • All issues related to any documentation should be tagged with this
  • importance_high
    Corelink
    Label to mark tasks as high importance. Decides the criticality of a task and a metric of impact to system. To be used in conjunction with issue priority labels
  • importance_low
    Corelink
    Label to mark tasks as low importance. Decides the criticality of a task and a metric of impact to system. To be used in conjunction with issue priority labels
  • issue_type_bug
    Corelink
    To be used to tag issues which are tasks for system bugs found in production
  • To be used to tag issues which are tasks for system bugs found in development
  • issue_type_epic
    Corelink
    To be used to tag issues which are tasks for broader topics. User stories should have sub tasks associated with them
  • Issues where features specs are requested and captured
  • issue_type_task
    Corelink
    To be used to tag issues which are tasks for new development/ enhancements
  • To indicate that the issue lacks proper information and description, tags, assignees, etc.
  • priority_high
    Corelink
    Highest priority issues. Is breaking the system and leaves things unusable
  • priority_low
    Corelink
    Medium level priority tasks. The bug/ issue can be lived with, but a fix is definitely needed.
  • priority_normal
    Corelink
    Urgent issues, but workaround can be applied.
  • state_blocked
    Corelink
    Issues which are blocked by another task
  • Issue state - In Analysis. Issue is assigned and is being analysed by people
  • Issue assigned to someone and is being worked on
  • state_in_review
    Corelink
    Issue is in code review post changes