How to prepare an issue triage table with useful evidence
An issue triage table helps a team review selected reports using consistent columns. It should make uncertainty and missing context easy to spot before assigning priorities or owners.
Start with the right material.
- What you provide
- a loaded issue list with readable labels and status.
- The intended result
- Export visible issue title, link, labels and status without reading unloaded discussions.
How the workflow works.
Preserve issue identifiers, titles and current status, then summarize the supplied impact and next question. Apply any provided classification rubric with a reason that a reviewer can inspect.
What to check in the result.
Compare the rows with the selected issue list and confirm exceptions before changing records. A generated suggestion is not an accepted priority, assignment or resolution.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Issue, Title, URL, Labels, Status. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.