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.

  • Danny Archer
  • Mar 16 2016
  • Future consideration
Release time frame
  • Attach files
  • Terry Matthews commented
    June 30, 2016 21:55

    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.

  • David Vins commented
    August 8, 2018 04:29

    How is this a "Future Consideration" and not a bug?!