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 |
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.