RELATED IDEAS
Improve syncing fixed workflows with integrations
What is the challenge? |
When statuses are mapped as bi-directional in integrations (Jira etc.) - transitioning rapidly between statuses in a fixed workflow in Aha! does not send each transition to the dev tool. With a fixed workflow in the dev tool, it is expecting to receive each status in the fixed order and will return an error because of the transition timing. |
What is the impact? |
Statuses are out of sync and errors cannot be resolved |
Describe your idea |
Improve how status transitions are sent from Aha! to an integrated dev tool when fixed workflows are expected to follow a certain order |
-
-
-
-
-
-
-
-
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved
Additionally, allow for some transitions in an Aha! fixed workflow to not be displayed in the UI and only available to the integration. e.g. in my org transition from "In Progress" to "Done" should only be done by the engineering team in Jira, and not be available to the PM in Aha!. But if I remove the button from the workflow, the Jira integration can't change the status from "In Progress" to "Done" either. Can we have the option for a transition in a fixed workflow to not display in the Aha! UI?
This is really really challenging for organizations with many many dev tool boards and many workspaces - managing workflows against fixed transitions is very difficult and requires too much coordination.