Skip to content
NEWMarketplace and the trig8n Agent: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Tasks & Project Management

Tasks & Project Management

Turn TeamRetro standup blockers into Jira issues with OpenAI and Slack

When a TeamRetro standup closes, OpenAI triages new blockers into Jira issues and comments on carried-over ones until they clear.

What it does

## TeamRetro: Turn standup blockers into Jira issues and follow them until they clear For engineering managers whose standup blockers get said once and lost. When a TeamRetro standup closes, OpenAI triages each new blocker and the actionable ones become Jira issues. A carried-over blocker is matched back to its issue, which gets a comment every staleAfter standups it stays open and a last one when it clears. ### How it works 1. The TeamRetro Trigger fires on Standup Completed. A delivery TeamRetro retries is skipped, so nothing happens twice. 2. Each update under your blocker question is sorted against the series' open issues. 3. Carried over: the issue moves to today's update, and Jira gets a comment when the blocker is overdue. 4. Cleared: its owner posted without carrying it over, so the row goes and Jira gets a comment. 5. New: OpenAI returns whether it is actionable, a category and an issue title. Actionable ones become Jira issues, are remembered in the standup_blockers Data Table, and are announced in Slack. ### Setup - [ ] Create a Data Table named standup_blockers with columns: updateId, issueKey, meetingSeriesId, personId, text (strings) - [ ] Copy the Production URL from "When Standup Closes" into TeamRetro under Settings → Integrations → Webhooks, tick Standup Completed, and paste the signing secret back into the trigger - [ ] Set jiraUrl, teamChannel and staleAfter in "Settings" - [ ] Connect OpenAI, Jira and Slack, and pick the Jira project and issue type Sample data is pinned. Running the pinned sample a second time stops at "Skip Repeat Deliveries": that is the duplicate guard. ### Customization Add labels or a priority under Additional Fields on "Create the Jira Issue". To close cleared issues, add a Jira transition after "Comment That It Cleared".

The steps

  1. When Standup Closes
  2. Skip Repeat Deliveries
  3. Settings
  4. Load Open Issues
  5. Sort the Blockers
  6. New, Carried or Cleared?
  7. Triage the Blocker
  8. OpenAI GPT-5 Mini
  9. Parse the Result
  10. Actionable?
  11. Create the Jira Issue
  12. Remember the Issue
  13. Announce in Slack
  14. Move It to Today

18 steps in total.

Similar automations