If everything is urgent, nothing is urgent.
A Sentry error is not automatically a Jira bug. Validate it first, then decide if it needs a Jira ticket.
Tickets reported by customers must be labeled customer-issue.
This helps us track customer-reported problems separately from internally discovered issues.
Share newly created Jira tickets in the team's dedicated channel.
Keeping all tickets visible helps the team stay informed, provide context, and avoid duplicate work.
Every piece of work must be created as one of the following:
| Type | Purpose |
|---|---|
| Bug | Something that worked before (or should work) but is broken |
| Task (Feature) | New functionality or enhancement |
| Epic | A large feature that consists of multiple tasks |
| Production Incident | An active production issue affecting users, revenue, or security |
Every Jira ticket must include: