Triage new issues before anyone has to
MergeHarbor reads new issues in Jira, Linear, Asana, GitHub and GitLab and keeps one comment on each, with possible duplicates, questions for the reporter, acceptance criteria and triage suggestions.
Possible duplicate: #412 Export fails for large orgs (similar stack trace)
Questions for the reporter:
- Which browser and plan were you on?
- Does it happen for exports under 1,000 rows?
Suggested: priority P2 · label export · owner @data-team · size M
How it works
Turn it on per project
Choose the projects, the parts of the comment you want and a monthly credit cap. Triage is off until you turn it on.
Read each new issue
MergeHarbor looks for similar issues, missing details and the likely code area, using your tracker's existing labels and components.
Suggest, then apply
Nothing changes on the issue until someone selects Apply suggestions, unless you turn on auto-apply for a project.
What you get
- One comment, kept up to date
- If an issue is triaged again, the same comment is updated, never repeated.
- Acceptance criteria that stick
- Proposed criteria are written as a checklist, and pull requests that link the issue are checked against them.
- Owners and size
- Suggested owners come from CODEOWNERS and recent authors, with a size from S to XL and the reason.
- Predictable cost
- A triage uses 1 credit, an unchanged issue is never charged twice, and each project has a monthly cap.
Frequently asked questions
Which trackers are supported?
Jira Cloud and Data Center, Linear and Asana through your integrations, and GitHub Issues and GitLab Issues on connected repositories.
Can triage open a fix?
For a likely root cause with a proposed change, Open fix PR opens a pull request against your default branch after you confirm. Root causes are off by default.
Have another question? Ask our support team
Review every pull request with the context of your whole codebase
Connect a code host in minutes. Reviews start right away, and codebase context is added as indexing completes.