The problem
A new bug report rarely tells you whether the team has already fixed the same failure. The earlier report may use different language or sit in a long backlog. Triage starts with two questions. Has this happened before? What should I do next?
What it does
Open a Jira issue and select Find related issues in TraceTriage. The panel ranks up to three issues from the same project and shows each key, title, status, and the summary terms, labels, or components it shares with the current issue. Click an issue key to inspect the report in Jira.
TraceTriage recommends one action. Review a likely duplicate when the summaries closely agree, investigate a related issue when the overlap is weaker, or triage manually when the search has little evidence. The panel is read-only. The person doing triage makes the decision.
How we built it with Forge
TraceTriage is a TypeScript app that uses Forge UI Kit's native Jira issue panel and Forge Bridge to read Jira's REST API with the viewer's permissions. It fetches the fields needed for triage and searches a bounded set of issues in the current project. A scoring rule compares normalized summary terms, shared labels, and shared components. Each result shows the overlap that contributed to its rank. The app has no external service to configure.
Install and try it
- Open the TraceTriage production install link as an admin on a Jira Cloud test site. Click Get app, select your Jira site, and click Install. The production app requests Jira work read access and needs no additional services or configuration.
- Open a Jira issue you can edit. Choose View app actions → TraceTriage → Find related issues. Open the key on any suggested match to inspect the original Jira report.
- To reproduce the video, create an empty company-managed Jira Software project with the Scrum template and a Jira component called Billing. Create these four synthetic bugs in that project.
| Bug summary | Jira status | Label | Component |
|---|---|---|---|
| Webhook delivery retries generate duplicate invoices after timeout | To Do | webhook-billing |
Billing |
| Webhook delivery retries generate duplicate invoices | Done | webhook-billing |
Billing |
| Webhook delivery queue stalls during invoice export | In Progress | webhook-billing |
Billing |
| Sidebar keyboard focus skips profile menu | To Do | profile-navigation |
Leave empty |
Run TraceTriage on the first bug. Expect Review a likely duplicate, with the earlier invoice report first and the queue stall second. The first result's key should open the earlier invoice report. Run it on the keyboard-navigation bug to see Triage manually. If issues were just created, wait until they appear in Jira search before testing.
The video is an edited walkthrough captured from the installed Forge production app on Jira Cloud. It uses synthetic tickets and computer-generated narration.