RELATED IDEAS
Automation rules send to integration
Rather than have to manually push ideas to the integration with Azure, Jira or other systems, it would be helpful and reduce manual administration if the automation rules could include the capability to send on a condition such as a status change.
For example: when a story moves to ready to develop, it is automatically sent to the external integration.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
5
MERGED
Add Automation Rule Action to Trigger Link/Send to ADO Integration
When a Release has been agreed on and finalised you want to send the items through to ADO for developers to start work on then based on a Release Status or individual Feature Status (or other criteria) to Send the Features through to ADO based on ...
0
Shipped
11
MERGED
Set feature initial status on "Send to jira"
It would be nice to have a status set on the first send to jira.
I have for example configured in jira integration page:
Status "New" in Jira -> Status "In design" in Aha.
So when I click the "Send to jira" button in the feature is should...
4
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
It will be great to setup a rule that automatically triggers the Aha-Jira integration.
We would love to see this in the automation rules as well. Is there a schedule for the implementation?
This is logical and fully endorse. Automatically sending "on create" could create issues, but upon status shift, would be logical. I realize there could be issues or concerns with this (e.g. if there is more than one integration in a workspace, etc.) but we're willing to set the conditions or configuration where Aha! workspace to Jira Project was 1-1 integrated.