Force Status field to be in sync with Jira

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:

• having a new two-way sync option where changes are reverted on failure. So if somebody changed the Status and it didn't take, it just doesn't take and stays in sync.
• Making Status (and other sync-into-Aha! fields) read-only, so they can't be changed in Aha! and therefore always stay in sync.
• Have more sophisticated workflow options, where Aha! would honor or mandate status transition requirements like Jira. So either not allow me to go from Under Consideration to Shipped directly; or take the stepping stones for me. 

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.

Thank you!