Report a technical ticket
Record the problem while it is visible. A report is a signal for the team to evaluate, not a finished specification, commitment, or implementation plan.
Bugs, stories, feature requests, and customer requests all start here.
Prerequisites
- Access to Jira for product and engineering tickets.
- Enough of the problem to describe what you saw or what outcome is missing.
Report documentation defects in this repository with the documentation bug report instead.
Write the ticket
Use a short title that makes the problem recognizable, then provide only:
Type: Bug | Task | Story | Sub-task
Priority: P0 | P1 | P2 | P3
Problem:
Add a screenshot, link, environment, or reproduction note when it is already available. Do not delay the report to produce acceptance criteria, technical analysis, or an implementation proposal.
A customer request is still a signal. Record who asked and what they need. It does not become an external commitment until planning makes that distinction visible in Jira.
Example:
Type: Bug
Priority: P2
Problem: Saving a contact without an email shows no error and the save button
stays enabled.
Choose a type
Triage confirms the type. Use the closest match:
| Type | Use it for |
|---|---|
| Bug | Existing behavior that does not work as expected. |
| Task | Technical or operational work without a standalone user story. |
| Story | An outcome a user needs to achieve, including a feature request. |
| Sub-task | A child part of an existing ticket that is not independently released. |
Use Story for a feature request unless triage later splits it. Use Bug or Story for a customer request depending on whether current behavior is wrong or a new outcome is needed.
Propose a priority
Priority describes impact and urgency, not implementation difficulty:
| Priority | Meaning |
|---|---|
| P0 | An active critical failure requiring immediate response. |
| P1 | Serious impact requiring urgent attention. |
| P2 | Normal planned work. |
| P3 | A low-impact improvement or backlog candidate. |
The reporter proposes the priority; triage confirms it. Team response-time agreements, when defined, remain the authority for timing.
Expected result
The ticket contains enough of a signal for triage to route it or ask one specific clarifying question. The reporter is not responsible for designing the solution.
If you cannot file the ticket
Ask the receiving team to file it with the information you have. Do not wait for a complete reproduction, design, or estimate.
Next: Triage the ticket.