ENGINEERING

Weekly flaky-test scorecard with owner accountability

Every Monday this rolls up the open quarantine issues by owner, computes how long each has been flaky, publishes a Confluence scorecard.

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionPull open quarantine issues from LinearLinearLinear
  • LogicGroup by owner and compute age vs SLA
  • ActionPublish scorecard to ConfluenceConfluenceConfluence
  • OutputSlack-nudge owners past SLASlack

What it does

It produces a weekly accountability report on the flaky-test backlog. It pulls every open quarantine issue from Linear, groups them by assigned owner, measures how long each has sat unresolved, publishes a ranked Confluence scorecard, and nudges owners whose quarantined tests have aged past the agreed SLA.

When to use it

Use it once you have a quarantine pipeline producing issues and need to keep the backlog from rotting — turning "someone should fix this" into a visible, owner-by-owner scorecard the team sees every week.

How it works

  1. 1A weekly schedule triggers the rollup each Monday.
  2. 2Open quarantine issues are pulled from Linear with assignee and creation date.
  3. 3A logic step groups by owner and computes age, sorting by oldest and most-recurring first.
  4. 4A Confluence page is published or updated with the scorecard table and trend.
  5. 5Owners with tests aged past the SLA get a direct Slack nudge linking their overdue items.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.