Release v2.15.0
Stale ticket detection
Overview
Tickets that sit untouched can slip through the cracks. Stale ticket detection flags work that has gone unviewed longer than a threshold you set. Once a ticket crosses that line, it counts as stale, surfaces on your dashboard, appears in the issue table, and you can filter the table to see only stale items—so nothing quietly ages out of sight.
Turning it on
- Where: Settings → Issue settings.
- Enable: Turn on Enable stale ticket detection with the checkbox.
- Stale threshold: Set how many days a ticket can remain unviewed before it is marked stale (number input). Default: 2 days. Adjust the value to match how aggressively you want to surface idle work.
Dashboard
- Stale count: The dashboard shows how many stale issues are assigned to you—at a glance you can see whether you have work waiting for attention.
- View list: Use View list to open the list of stale issues where you are the assignee, so you can triage or pick up the next item without hunting through the full backlog.
Issue table
- Stale indicator: Stale status is visible on the issue table, so you can spot aging tickets while browsing or sorting like usual.
- Filter: Filter the table to show all stale issues when you want a focused pass over everything that has crossed the threshold—not just your own assignee queue.
Settings summary
| Control | Effect |
|---|---|
| Enable stale ticket detection off | Stale detection is inactive; dashboard count, list link, and stale styling/filtering do not apply. |
| Enable stale ticket detection on | Tickets unviewed longer than the stale threshold (days) are marked stale; dashboard, table, and filters reflect that state. |
| Stale threshold (days) | Number of days a ticket can be unviewed before it becomes stale (default 2). |
Issue priority levels
Overview
Every issue now has a priority level so teams can signal urgency at a glance. Priority is a required field when you create an issue (dropdown), and you can change it anytime when editing an issue. The app ships with three default levels; you can rename, adjust, or add levels under Settings → Issue priority levels.
Default priority levels
These levels are seeded for new environments. Each has a color, short description, and slug (used internally).
| Level | Color | Description | Slug |
|---|---|---|---|
| Low | Green | Low priority. Handle when time permits. | low |
| Medium | Orange | Medium priority. Should be addressed soon. | medium |
| High | Red | High priority. Needs immediate attention. | high |
Configuring priority levels
- Where: Settings → Issue priority levels.
- Customize: All default levels are editable. You can also create new priority levels to match your team’s workflow (for example, a “Critical” tier or a calmer naming scheme).
Existing issues and day-to-day use
- Upgrades: Issues that already existed in production default to Low priority so nothing is left unset.
- Create: Choosing a priority is required; use the dropdown on the create form.
- Edit: Open any issue and update its priority level whenever urgency changes.