Ticket Categories

  1. Epic: See description below
  2. Boulder: Usually a flow or group of screens that together make up a feature. 5 days or less
  3. Rock: Usually a new section or screen - .5 to 1 day
  4. Stone: Usually a small improvement e.g a new button that triggers an email to be sent. 1 to 2 hours
  5. Pebble: Usually a very small improvement eg add a validation to a field, copy update
  6. Bug
  7. Bug - Critical Anything that prevents a specific percentage of users from accessing a specific scope of important features (define as relevant).
  8. Bug - Regression
    • This is when a bug was introduced by another task, as opposed to just something that wasn't accounted for in the first place.
  9. Doc/Other
    • This is used when the “task” in asana is more of a record/document than a technical task.

Epics

  • Not all work can be done in less than a week. An Epic…
    • Is likely to take more than a week - often 2 to 3 weeks.
    • Often has a “migration/rollout” phase which contain tasks that are non-dev, but equally important.
    • Usually consists of multiple boulders that all need to be shipped at the same time.
  • Mid to long term roadmap items are also usually conceived of as epics, so the Epic concept can be useful for roadmap planning - brain dump in to the “Epics” tab in Asana.
  • We want to keep this in an easy-to-access place in Asana that doesn’t clutter up the itemised weekly tickets, so…
    • Separate view tab in Asana with filter set to only show tasks of type “Epic” → This is where the planning happens.
    • Add the broken-down-work as sub tasks, which in turn have their own task type and allocated week
    • When a new week starts, you
    • If it’s the final week of the Epic & it’s getting shipped, you can also set the