Reporting and Tracking Issues
Issues are bugs, defects, or problems that need to be investigated and fixed. In Varai Sprints, issues are managed alongside tasks in your sprints, giving your team a unified view of all work — both planned features and discovered bugs.
What is an issue?
An issue represents a problem that was found and needs to be addressed. Unlike tasks (which you plan ahead of time), issues are often discovered during testing, user feedback, or production monitoring.
Issues have:
- A title and description of the problem
- A severity (how bad is it?)
- A priority (how urgently should it be fixed?)
- A status that tracks progress from open to resolved
- An assignee responsible for the fix
- A sprint they are planned into
Creating an issue
From the Issues page
- In the left sidebar, click Issues.
- Click New Issue (top-right).
- Fill in the issue form (see fields below).
- Click Create Issue.
From within a sprint
- Open the sprint.
- Click Add Issue → Create new issue.
- Fill in the form.
- Click Create Issue.
The issue is immediately added to the sprint.
Keyboard shortcut
Press I in most views to open the new issue form.
Issue fields
| Field | Required? | Description |
|---|---|---|
| Title | Yes | A clear, concise description of the problem (e.g., "Login form does not clear on error") |
| Description | No | Steps to reproduce, expected vs actual behavior, screenshots |
| Severity | Yes | How serious is the problem? (Critical, High, Medium, Low) |
| Priority | No | How urgently should it be fixed? (Critical, High, Medium, Low) |
| Status | Auto | Starts as "Open" automatically |
| Assignee | No | Who is responsible for fixing this issue |
| Sprint | No | Which sprint this issue will be worked on |
| Planned start/end | No | When the fix is planned |
| Tags | No | Labels for filtering |
| Epic | No | Link this issue to an epic |
Include:
- Steps to reproduce — numbered steps to trigger the bug
- Expected result — what should happen
- Actual result — what actually happens
- Environment — browser, device, OS, app version (if relevant)
- Screenshots or video — attach evidence using the Attachments section
This helps whoever is fixing the issue understand the problem immediately.
Severity vs priority
Severity and priority are related but different:
| Severity | Priority | |
|---|---|---|
| What it measures | How bad is the impact? | How urgently should it be fixed? |
| Who sets it | QA / person who found the bug | Product manager / team lead |
| Example | Data loss = Critical severity | But the feature is rarely used = Low priority |
Both fields help your team make good decisions about what to work on first.
Assigning an issue to a sprint
Issues can exist in a backlog (no sprint) or be assigned to a specific sprint.
To add an issue to a sprint:
- Open the issue.
- Click the Sprint field.
- Select a sprint from the dropdown.
- The issue now appears in that sprint's board and list.
Or, from the sprint:
- Open the sprint.
- Click Add Issue → search for an existing issue → select it.
Tracking issue status
As work progresses on an issue, update its status:
| Status | Meaning |
|---|---|
| Open | Issue is filed, not yet assigned or started |
| In Progress | Someone is actively working on a fix |
| In Review | Fix is ready, awaiting review/testing |
| Resolved | Fix is confirmed and deployed |
| Won't Fix | Acknowledged but will not be fixed (explain why in a comment) |
| Closed | Issue is fully resolved and verified |