A product board that stays current: statuses and dates sync themselves

The scenario watches your teams' tasks and projects, translates their statuses into the product board's, updates status and dates there, and posts a note to chat.

  • The product board never drifts from what development is actually doing
  • Statuses are translated through your own mapping — the two systems name things differently
  • Projects and individual tasks are each updated the right way
  • The team hears about every change as a chat message
Productboard
Set this upScriptera

How it works

To keep botHelp and GitHub in sync, connect them with a ready-made scenario — changes flow automatically.

  1. Starts when: Core
  2. Then: mapping Linear status to Productboard status
  3. Then: get productboard feature id
  4. Then: Split Out
  5. Check: Project or Issue
  6. If yes: Linear URL in productboard Project
  7. Check: If match for project
  8. If yes: get productboard feature details
  9. Check: If linear action is update
  10. If yes: Project or Issue (2)
  11. If yes: Status or Date changed for Linear Project
  12. If yes: update productboard status & timeframe when Linear Project
  13. Then: Slack
  14. If no: Status or Date changed for Linear Issue
  15. If yes: update productboard status & timeframe when Linear Issue
  16. Then: Slack1
  17. If no: Linear URL in productboard Issue
  18. Check: If match for issue
  19. Starts when: NHI
  20. Starts when: Source
  21. Starts when: Private Incidents
  22. Starts when: Secret detection
  23. Starts when: Self-Hosted
  24. Starts when: ML

You can launch this botHelp + GitHub integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios