🪃
Engineering Playbook
  • Engineering Playbook
  • Agile Development
    • Kanban from the start
    • Daily Stand-up
    • Collaboration
      • Mobile Designer X Mobile Developer
    • Backlog Management
      • Backlog Refinement
    • Card Management
      • Epics
      • User story
        • Collaboration experience with acceptance criteria
        • Proper acceptance criteria
      • Task
      • Bug
      • Hotfix
      • Sub-task
      • Defect
      • Columns
      • Card organization
      • Column Limit
      • Board Templates
    • Pull System Task Assignment
    • Retrospectives
    • Team Agreement
      • Working Agreement
      • Definition of Ready
      • Definition of Done
    • Agile Metrics
  • Github
    • Source Control
    • Merge Strategies
    • Versioning
    • Code Reviews
      • Author's Checklist
      • Reviewer's Checklist
  • Documentation
    • GraphQL as an API Doc
  • DevOps
    • Continuous Integration
Powered by GitBook
On this page
  • Naming title guidelines
  • Writing a description guidelines

Was this helpful?

  1. Agile Development
  2. Card Management

Hotfix

PreviousBugNextSub-task

Last updated 3 years ago

Was this helpful?

Unlike bug cards, this card should be tested solely by developers who fixed this and bypassed the QA-related pipelines before releasing it to production.

Naming title guidelines

Example(s)

New user can't view homescreen

NOTE: There are several ways to format the title of a Hotfix card.

Please see

Writing a description guidelines

Add more details to guide the developer(s), like screenshots and narrowing down scenarios.

Example(s)

New user can't view homescreen when certain events

Naming Hotfix Cards