RELATED IDEAS
Support JIRA issues being unassigned
If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
© 2024 Aha! Labs Inc.•All rights reserved
How is this a "Future Consideration" and not a bug?!
I'm also seeing the same in the other direction, i.e. when you set the Aha! feature to unassigned, it doesn't update Jira.