Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • Unexpected
    caosdb
    An issue that came up during a sprint and needs immediate treatment, i.e. it can not wait until the next sprint.
  • Triage
    caosdb
    The triage is the state before any life-cycle begins. The assigned triagers decide which kind of issue is in front of them and hence which life-cycle the issue should to follow.
  • Task of Shame
    caosdb
    A task that took much longer than expected from its complexity, due to bad DoDs, unexpected pitfalls, etc.
  • Task
    caosdb
    A task is anything which does not fit into any other life-cycle and this particular state represents the uncompleted task.
  • Statustodo
    caosdb
    Will be done in current sprint
  • Statusnext
    caosdb
    This issue describes issues for the next sprint
  • Statusdoing
    caosdb
    will be done today / is ongoing
  • StatusReview
    caosdb
    The feature or bug fix has been impleted, documented where necessary and tested by the developer and is now under review. This label should be removed after the last reviewer has reviewed the proposed resolution.
  • Shitty Title
    caosdb
    This issue has a really shitty title
  • S4
    caosdb
    Severity 4 - Low: Functionality inconvenience or cosmetic issue.
  • S3
    caosdb
    Severity 3 - Major: Broken Feature, workaround acceptable.
  • S2
    caosdb
    Severity 2 - Critical: Broken Feature, workaround too complex & unacceptable.
  • S1
    caosdb
    Severity 1 - Blocker: Outage, broken feature with no workaround.
  • Question
    caosdb
    This issue is a question or a problem that can be answered by a person with enough information.
  • P3
    caosdb
    Priority: 3 (Low)
  • P2
    caosdb
    Priority: 2 (Medium)
  • P1
    caosdb
    Priority: 1 (High)
  • Order
    caosdb
    When an issue is worked on due to a (paid) order, no matter whether the payment is per hour or fixed.
  • On Hold
    caosdb
    The assignee cannot proceed with this issue due to dependency on another issue which needs to be closed or at least reach a certain state first.
  • This issue is well-suited for newcomers without any specific experience in developing LinkAhead.