The recommendation of keeping Status as a one way sync from Jira makes Aha! reports silently unreliable, as Aha! and Jira status will diverge if somebody touches a record "by mistake".
If I set it to two-way sync, transitions not allowed by Jira make things go out of sync with a notification. I get a message that integration sync failed, but I can only ignore the change and not revert it, so I'm out of sync right away.
I'm thinking a couple of options could address this, like:
Right now I would have to periodically update the Aha! records from Jira, which is very painful, or run the report in Jira which not that great.
You can now enforce that a specific status order is followed in Aha! Configure your status workflow as 'fixed' and define the allowed status transitions.