Prioritized Labels
  • Story: Bug
    Crown
  • Other Labels
  • Severity: Critical
    The defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.
    Crown
  • Status: New/Suggestion
    New suggestion to build a feature/user story, product enhancement, bug etc.
    Crown
  • Story: User Story
    Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template: As a < type of user >, I want < some goal > so that < some reason >.
    Crown
  • Status: In-Progress
    The issue is in development.
    Crown
  • Status: Code-Review
    The issue is under peer code review.
    Crown
  • Status: QA
    The issue is fixed/implemented and is waiting for approval from the QA team.
    Crown
  • Component: MN-Budget Governance
    Crown / crown-core
  • Component: Systemnode
    Crown / crown-core
  • Component: Masternode
    Crown / crown-core
  • Component: Wallet-UI
    Crown / crown-core
  • Component: JSON-RPC API
    Crown / crown-core
  • Component: Mining
    Crown / crown-core
  • Component: Update
    Crown / crown-core
  • Component: Transport
    Crown / crown-core
  • Component: Instant-Send
    Crown / crown-core
  • Other: Upstream
    This issue should be fixed/implemented in the upstream repository
    Crown
  • Severity: Major
    The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.
    Crown
  • Severity: Minor
    The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.
    Crown
  • Severity: Trivial
    The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.
    Crown
  • Importance: 16