Skip to Main Content
Status Future consideration
Created by Ronnie Merkel
Created on Feb 17, 2021

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.

  • Attach files
  • Donald Hebert
    Apr 14, 2023

    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.

  • +2

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 ...
Dave Ball about 3 years ago in Azure DevOps Services and Server 0 Future consideration