Issue Tracker
The Issue Tracker is your control center for monitoring and managing issues related to your virtual assistant. Whether it's a bug report, a feature request, or an improvement suggestion, this section helps you stay on top of everything that requires attention.
New Feature The Issue Tracker was released in June 2025 and is currently in beta testing. Learn more about this new feature here: Issue Tracker for Tests & Improvements
π The Issue Tracker Dashboard
The dashboard offers a streamlined view of all open, in-progress, and resolved items in your workspace.

Each issue is displayed in a table format with key details:
Identifier β A unique code like
AZI-20
, automatically generated.Priority β Visual indicators (e.g., bar icon πΆ) show urgency (Low, Medium, High).
Subject β The issue title for quick recognition.
Created / Last Edited β Track timestamps for audit and update history.
Tags β Labels like βBugβ or βImprovementβ for classification.
Comments β Indicates collaboration level on the issue.
You can also:
Use the search bar π to locate specific issues.
Apply filters β to narrow down by status, tag, or date.
Click Create Issue to open a new issue form.
Use the calendar selector π to explore issues on specific dates.
π Creating a New Issue
Click the β+ Create Issueβ button at the top right of the dashboard.

From here, you'll access a form where you can enter all necessary details:
Subject β Title of the issue.
Requester β Who reported it.
Assignee β Person responsible for resolving it.
Source β Environment (e.g., Production).
Priority β Set importance (High, Medium, Low).
Status β Track workflow (Backlog, In Progress, Resolved).
Tags β Add context (e.g., Bug, Improvement).
Description β Add a detailed explanation of the problem or feature.
Comments β Discuss directly within the issue thread.
You can edit or delete any issue using the respective βEditβ or βDelete Issueβ options at the bottom of the issue detail view.

π Managing and Prioritizing Work
Once created, issues move through different stages:
Backlog β Newly created items awaiting triage.
In Progress β Actively being worked on.
Resolved/Closed β Completed or no longer needed.
Use Tags to group issues into themes like:
Bug β Technical issues or malfunctions.
Improvement β UX enhancements or backend optimizations.
Feature β New functionalities or requests.
Assigning a priority level ensures high-impact items get tackled first. This is especially useful for large teams or complex environments.
π¬ Collaboration and Transparency
Each issue supports a comment thread, making it easy to:
Share updates.
Ask questions.
Record decisions.
This ensures everyone stays alignedβno need to jump into external tools or chats.
β
Best Practices
Keep descriptions detailed so assignees understand the context.
Use tags consistently for better filtering and reporting.
Update status and priority regularly to reflect current progress.
Encourage commenting to keep communication centralized.
Last updated
Was this helpful?