Labels

• 1

  burning issue
• 1 hour

  typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
• 15 mins

  small issues. Usually cosmetic fixes
• 2

  performer can implement issue at his closest convenient time
• 2 hours

  some big and monolith issues. For example with hard decisions or discussions
• 3

  we can defer this issue. But it'll good to implement it
• 30 mins

  small issues. Usually cosmetic fixes
• Admin renew

  adapt admin to the options, tag and db templates integration
• Backup

  feature
• blocked

  issue is blocked by another issue
• blocker

  this issue blocks another issue
• bug
• cleanup

  everything that do project stronger, flexible, reusable
• Data

  Feature about migrating data on prod
• dependencies

  Pull requests that update a dependency file
• devops

  work with service options with code or with configs
• discuss

  issue needs to finish discussion before start working
• docs

  issue for improving project's documentation
• duplicate
• easy

  new teammates can start with such issues to become familiar with project
• feature

  issue provides some new functionality for project users
• from business
• from PO

  from product owner. It's hellxi
• from seo
• front

  markup or work with js
• Front structure
• hard

  issue requires strong architecture skills, management skills, project domain area, etc
• invalid
• monitoring
• needs info

  issue needs additional requirements to start working