LogoLogo
PAO DocsInfrastructure DocsDeveloper DocsPeerplays.com
  • Introduction to Peerplays
  • Concepts
    • Decentralization
    • Consensus Mechanisms Compared
  • Technology
    • Peerplays Technical Summary
    • Intro to Peerplays Tokens
    • Intro to Peerplays Liquidity Pools
      • Service Infrastructure Pools
    • Staking (PowerUp) in Peerplays
    • Gamified User Namespaces and Subject Matter Expert Committees
    • Peer-to-Peer Autonomous Organizations: Flow Diagram
    • Gamified Proof of Stake (GPOS)
      • Wallet User Guide
        • GPOS Panel
        • GPOS Landing Page
        • Power Up
        • Power Down
        • Vote
        • Thank you for voting!
      • FAQ
        • General
        • GPOS Panel
        • Power Up & Power Down
        • Voting
        • Participation Rewards
    • Sidechain Operator Nodes (SONs)
      • New to SONs?
        • What are Sidechain Operating Nodes?
        • How do SONs Work?
        • Why are SONs important?
        • How do SONs impact me?
        • SON Fees & Performance Requirements
        • Peerplays SONs
      • FAQ
      • Running a SON Node
    • NFTs and Marketplace
      • NFT marketplace in Python
      • NFT Operations in Python
      • NFT, Marketplace, HRP, and RBAC related Commands/Use Cases
      • NFT command reference
    • Peerplays DEX
      • User Guide
        • Account Creation
        • Dashboard
          • Bitcoin Transaction
        • Market Activity
        • Peerplays Blocks
        • Settings
        • Wallet
        • Profile
        • GPOS - Voting
        • Logout
  • Witnesses
    • What is a Peerplays Witness?
    • Becoming a Peerplays Witness
    • Hardware Requirements
    • Installation Guides
  • Bookie Oracle Suite (BOS)
    • Introduction to BOS
    • BOS Installation
    • BookieSports
    • Manual Intervention Tool (MINT)
  • Data Proxies
    • Introduction to Data Proxies
    • How Data Proxies Work
    • Data Proxy Set Up
  • Couch Potato
    • Introduction
    • Installation
    • User Guide
  • Random Number Generator (RNG)
    • RNG Technical Summary
    • RNG API
  • API
    • Peerplays Core API
      • Popular API Calls
      • Account History API
      • Asset API
      • Block API
      • Crypto API
      • Database API
      • Network Broadcast API
      • Network Nodes API
      • Orders API
    • Wallet API
      • Account Calls
      • Asset Calls
      • Blockchain Inspection
      • General Calls
      • Governance
      • Privacy Mode
      • Trading Calls
      • Transaction Builder
      • Wallet Calls
    • Bookie API
      • General
      • Tournaments
      • Listeners
    • Python Peerplays
      • Installation
      • Creating the wallet
      • Creating an Account
      • NFT
      • Market Place
      • HRP / RBAC
  • Connecting Elasticsearch to a blockchain node
  • GitLab
    • GitLab Ticket Templates
    • Labels
    • Time Tracking
  • Other Documentation
    • Peerplays Home
    • Infrastructure Docs
    • Developer Docs
    • Site Reliability Engineering
  • Known Issues
    • Peerplays Disaster Recovery Plan
    • Sept 2021 Mainnet Outage - Postmortem Report
  • Kickstart Guide
    • Peerplays Developer
  • Risk Register
    • Introduction
      • Bunker Issue
        • DDOS Attack
        • Hypervisor Compromised
        • Power and Backup Failure
        • Crypto Restriction
      • Core-Block Issue
        • Expensive Servers
        • Witness node - Not reachable
        • Witnesses get DDOS'd
        • Bad Actor infiltrate witness/SONs
      • Credential Security
        • NEX Open Source Vulnerabilities
        • Keyloggers, access to NEX deployment
        • Password manager hacked
        • SONs active keys exposed in configuration
    • Glossary
  • Operation Cost Estimation
    • Project Operations
    • Cost Estimation
Powered by GitBook
On this page
  • Scoped Labels
  • Priority::
  • State::
  • Type::
  • Other Labels
  • Issue Lifecycle
  • Glossary
Export as PDF
  1. GitLab

Labels

PreviousGitLab Ticket TemplatesNextTime Tracking

Last updated 4 years ago

Scoped Labels

The scoped labels (ending with ::) are mutually exclusive. Only one of these labels can be assigned at a time to an issue.

Priority::

  • low

  • medium priority

  • high priority

  • critical priority

State::

  • pending

  • accepted

  • in progress

  • in review

  • in testing

  • completed

  • on hold

  • blocked

  • revision needed

Type::

  • bug

  • feature

  • documentation

  • question

  • maintenance

Other Labels

  • duplicate

  • discussion

  • security

Issue Lifecycle

All issues should have a state and type scoped label attached to them. The following is a proposed lifecycle an issue should have:

  1. Pending - Issues that are newly created and haven't been reviewed.

  2. Accepted - Issues that are newly created and have been accepted after review.

  3. In Progress - Issues that are currently being worked on.

  4. In Review - Issues that require a proposed solution to be reviewed.

  5. In Testing - Issues that require a proposed solution to be tested.

  6. Completed - Issues that are closed with a working solution.

This will cover a standard lifecycle of an issue. There are other state labels for issues that are not being worked on:

  • On Hold - Issues that were at least accepted, that should not be worked on at the moment.

  • Blocked - Issues that cannot be worked on due to other factors linked to it.

  • Revision Needed - Issues that need to be revised before being accepted.

Glossary

Label

Description

priority::low

(optional) Issues that are marked as low priority.

priority::medium

(optional) Issues that are marked as medium priority.

priority::high

(optional) Issues that are marked as high priority.

priority::critical

(optional) Issues that are marked as critical priority. Should be taken care of ASAP.

state::pending

Issues that are newly created and haven't been reviewed.

state::accepted

Issues that are newly created and have been accepted after review.

state::in progress

Issues that are currently being worked on.

state::in review

Issues that require a proposed solution to be reviewed.

state::in testing

Issues whose proposed solution is being tested.

state::completed

Issues that are closed with a working solution.

state::on hold

Issues that were at least accepted, that should not be worked on at the moment.

state::blocked

Issues that cannot be worked on due to other factors linked to it.

state::revision needed

Issues that need to be revised before being accepted.

type::bug

Issues that are an unexpected, or incorrect result in the project.

type::feature

Issues that bring new functionality to the project.

type::documentation

Issues that relate to the documentation of the project.

type::question

Issues that are questions related to the project.

type::maintenance

Issues that require maintenance on the project.

duplicate

(optional) Issues that are duplicates of existing issues in the same project.

discussion

(optional) Issues that discuss specific project changes.

security

(optional) Issues that relate to the security of the project.

https://gitlab.com/groups/PBSA/-/labels