Aha! Teamwork Advanced plan required. Contact us if you want a demo, or to try using this in your account. No salespeople here at Aha! — just product experts.
This article is part of a series of settings overview articles:
Account |
Team |
Personal |
If you are an Aha! Teamwork Advanced plan customer, you can automatically sync the status of records in Aha! Teamwork with the rest of your dev tools — like GitHub, GitLab, and CircleCI. Open your team status automation settings by navigating to Settings ⚙️ -> Team. You will need to be an owner to do this.
These settings configure status automation rules for any official Aha! Teamwork extension.
Click any of the following links to skip ahead:
Status automation
The status automation settings are organized around every workflow extension you have enabled in your Aha! Teamwork account. Make sure you have also added an extension's view contribution fields to the relevant record types' custom layouts so you can see the related builds and PRs.
Click on an extension to get started.
On the left of the Extension status automation modal, you will see every Extension event that can trigger a status change on an Aha! Teamwork record.
On the right of the modal, you have your Team status workflow.
For any Extension event, choose the status you want your Aha! Teamwork record to move into. For example, a PR opened event could move the linked Aha! Teamwork record to Ready for code review status.
If you have connected Aha! Teamwork and Aha! Roadmaps, you can also map statuses between the two tools. An extension status automation can trigger an Aha! Roadmaps status automation. For example, a PR merged event could automatically move your Aha! Teamwork team status to Ready for PM review. That could automatically move the record's Aha! Roadmaps workspace status to Ready for PM review as well. By merging a PR, you would have automatically alerted the product team that the item is ready for them.
Potential automations
You can configure status automation rules for any official Aha! Teamwork extension. These are the currently possible extension events that can trigger a status change on an Aha! Teamwork record.
Azure Pipelines
Trigger |
Invoked when... |
Build passed |
A build pipeline passes |
Build failed |
A build pipeline fails |
Azure Repos
Trigger |
Invoked when... |
Draft PR opened |
A new draft PR is opened |
PR opened |
A new non-draft PR is opened |
PR merged |
A PR is merged into the target branch |
PR closed |
A PR is closed without merging |
PR approved |
A PR is approved by a reviewer |
Changes requested |
A reviewer requests changes on a PR |
CircleCI
Trigger |
Invoked when... |
Build passed |
A CI build passes |
Build failed |
A CI build fails |
GitHub
Trigger |
Invoked when... |
Draft PR opened |
A new draft PR is opened |
PR opened |
A new non-draft PR is opened |
PR merged |
A PR is merged into the target branch |
PR closed |
A PR is closed without merging |
PR approved |
A PR is approved by a reviewer |
Changes requested |
A reviewer requests changes on a PR |
GitLab
Trigger |
Invoked when... |
Draft PR opened |
A new draft PR is opened |
PR opened |
A new non-draft PR is opened |
PR merged |
A PR is merged into the target branch |
PR closed |
A PR is closed without merging |
PR approved |
A PR is approved by a reviewer |
Changes requested |
A reviewer requests changes on a PR |