Issues

Types

Issues should describe actionable items that can be finished. They are either:

• A single task ticket that describes a single unit of work that needs to be done. It doesn’t depend on other tickets.
• An overarching ticket that describes a smaller part of an ‘EPIC’ and has a list of TODOs that link to single task tickets.
• An overarching ticket that describes a feature on a high-level, and which in turn has a list of TODOs that link to tickets that describe smaller parts of the requirement. This is an ‘EPIC’ and should be assigned to the engineer that ‘owns’ the feature implementation.

As rich as possible information should go into each ticket, at the right level of abstraction. E.g. details about ‘WebSockets’ go into the ‘Experiment with WebSockets’ ticket, not the ‘Live Auction’ EPIC.

To ensure they are rich and up-to-date, it’s perfectly fine to update a issue, amendments and additions do not need to be in comments, but it may be helpful to notify others after updating.

Classification

Term	GH Tool	Standardization	Examples
Team (T)	Label	across teams	‘T: Auctions’
EPIC	Label	across teams	‘EPICs’
Sprint	Milestone	team specific	‘Auctions Sprint Feb 15 - Feb 26’
Global Milestone (GM)	Label	across teams	‘GM: Live Bidding’, ‘GM: Artist Views’
Pipeline	–	GM specific	‘Backlog’, ‘In Progress’
Team Dependency (TD)	Label	across teams	‘TD: C&GMV Web’
Blocker	Label	across teams	(no current example exists)