Skip to content

Labels

Labels

  • bug

    Something isn't working
  • duplicate

    This issue or pull request already exists, or the discussed topics have already been addressed.
  • effort: 1

    Very low. Minimal implementation effort usually without upfront preparation (a couple of hours).
  • effort: 2

    Low. Minimal implementation effort, possibly with upfront preparation (a couple of days).
  • effort: 3

    Medium. Implementation can be planned as successive scrums (a couple of weeks).
  • effort: 5

    High. Implementation requires a dedicated milestone & some planning (a couple of fortnights).
  • effort: 8

    Very high. Project planning and a WBS need to be established (a couple of months).
  • effort: n

    Unknown. Project planning and a WBS need to be established (Fibonnaci >= 13).
  • help wanted

    Project team requires community help.
  • prio: critical

    An SLA severity level 2 has been triggered.
  • prio: emergency

    An SLA severity level 1 has been triggered.
  • prio: high

    Immediate action is required.
  • prio: medium

    Topic is a concern and should be considered rapidly.
  • prio: plan

    Topic has yet to be scheduled.
  • prio: schedule

    Topic is scheduled for next milestone.
  • scope: build system

    Focus is on the build system.
  • scope: documentation

    Improvements or additions to documentation
  • scope: infrastructure

    Focus is on the underlying infrastructure for production and other environments.
  • scope: master data

    Focus is on master data management/migration
  • scope: source code

    Focus is on the source code (default).
  • scope: testing/uat

    Focus is on testing on a particular UAT run.
  • stage: build

    Lifecycle stage: build.
  • stage: deploy

    Lifecycle stage: deploy (and devops).
  • stage: design

    Lifecycle stage: design.
  • stage: run

    Lifecycle stage: manage & run.
  • stage: shutdown

    Lifecycle stage: shutdown & decommission.
  • stage: test

    Lifecycle stage: test (more specifically UATs).
  • state: approved

    Issue/pull request has been approved and dependent actions may now be enacted.
  • state: blocked

    Issue/pull request has been blocked and all related on-going activities should be paused.
  • state: completed

    Issue has been completed (redundant with `closed` status).