| Table of Contents |
|---|
Introduction
I have previously written a lightning talk introducing some helpful patterns for writing JIRA tickets. It introduces some terminology, as well as what should be expected from a fully-detailed ticket.
The purpose of this document is to supplement those definitions with examples of breaking down larger work items to increase transparency into the process and maintain forward momentum.
Hints / Steps for Breaking Things Down
...
NOTE: If you do manage to tease out one or more new issues, link it back to the original by clicking Link Issues and choosing "split from" or "split to"
Warning Signs / Red Flags
The following may not always be a bad thing, but they can indicate an issue that can be further broken down
...
- Expand admin-only Extractor Catalog to make it public
- Add additional information to this view (e.g. version, rating, comments, etc)
- NOTE: While there were lots of unanswered questions, this discussion did match up fairly well with the original ticket text
...