Steps your tools could automate
Ovenbird points out steps your tools could do by themselves, such as CI posting in Slack, and how to set them up.
Some steps are things a tool could do the moment it knows: telling QA a build is ready, moving the Jira issue when a pull request is merged, writing the release notes. Ovenbird looks for them and suggests how.
Where you see them
- In the Studio, in the Checks panel: 💡 Could be automated, one card per step. The ⚠ Checks button shows how many, and the step has a 💡 on the board. Selecting the step shows its suggestion too.
- On Design → Processes (owners, admins and designers): "N steps in M processes could be automated", with the list and a link to each board.
AI review looks for more, from the same list of integrations.
What a suggestion says
- What would happen, for example "CI posts the build result in Slack", and why it fits that step.
- Uses: the tools involved, marked connected when they're connected to Ovenbird.
- How to set it up: what to do in those tools (for example, add the GitHub app to the Slack channel and subscribe it to the repository's workflows), and roughly how long it takes.
- Then the step becomes: the step's new wording, for example "Automatic: the CI build result is posted in Slack".
Ovenbird doesn't set anything up in your tools: you do it there, then check it works.
Mark as automated, or Not now
- Mark as automated once it's set up. The step shows ⚡ on the board, and once you publish, the runbook shows "⚡ Automatic: …" with what the step used to say. /nextstep and the course then treat it as something a tool does, not a person. A person does it again (on the selected step) undoes it.
- Not now hides that suggestion for that step.
What it covers today
Software teams' tools: GitHub and CI, Jira, Slack and Freshdesk. For example: build and deploy results in Slack, review requests in Slack, pull requests linked to and moving their Jira issue, release notes from GitHub or a released Jira version, required checks before merging, and Freshdesk tickets escalated to Jira and kept in sync. Suggestions only use these known integrations; approvals, decisions and conversations with customers are never suggested.
Still stuck? Ask your workspace owner or an admin, or get in touch with us.