Issue triage

New issues labelled, prioritized and assigned every morning.

New issues pile up unlabeled, with no owner and no priority. Hops triages them every morning so the team starts the day with a sorted queue.

How it runs: Scheduled. An automation runs every day at 9am, posts the triage summary and updates a Table. You can also ask Hops any time.

What it does

• Reads every new issue. Hops checks Linear, Jira or GitHub Issues for items created since the last run.
• Labels by area. Each issue gets the area label that matches your area map.
• Sets priority from impact and reach. Hops explains the reasoning in one line.
• Links duplicates and suggests owners. Duplicates are linked, and owners come from the area-to-owner map in Space context.
• Flags outages as Urgent. Anything that looks like an outage is called out at the top of the summary.

Ask Hops

Copy a prompt into any chat with Hops, or mention @Hops in a Space.

Triage the new issues in the Acme web project from the last 24 hours.

Which new issues look like duplicates of existing ones?

Suggest owners for the 6 unassigned issues using our area map.

Are any of this week's new issues possible outages?

Show me this week's triaged issues grouped by area.

Example reply:

Triaged 14 new issues:

• 1 Urgent: checkout returns 500 for EU customers.
• 3 duplicates linked to existing issues.
• 9 labeled and assigned, 1 needs a human to pick an area.
• Biggest area this week: billing, 5 issues.

What you get

• A morning post. The summary appears in the Space chat or your Slack channel at 9am.
• An updated Table. Triaged issues are added to a triage log in Tables in the Space, with area, priority and owner.
• Answers on demand. Ask Hops to re-triage or explain a decision at any time.

Connections needed

Connect these apps. Each card opens Connections in the app.

Linear

New issues and labels.

Jira

New issues and labels (or Linear).

GitHub

GitHub Issues (or Linear or Jira).

Slack

Where the triage summary is posted.

Set it up

1. Connect your apps

   Connect Linear, Jira or GitHub Issues, and Slack in Connections.

   See Connections.

2. Create the Space

   Create a product-eng Space and pin the area-to-owner map in Space context.

   See Spaces and Space context.

3. Add the skill

   Give Hops these instructions:

   You triage new issues. Label each by area, set priority from impact and reach, link duplicates, and suggest an owner from the area map. Flag anything that looks like an outage as Urgent.
   

   See Build a skill.

4. Schedule it

   Create an automation that runs every day at 9am. It posts the triage summary to the Space and updates the triage log in Tables.

   See Automation.