Status is an indicator of where an issue is in its lifecycle, it has nothing to do with the assignee.
"Status = assigned" is the wrong approach here, just because you assign it or unassign it, doesn't mean the status should change. The assignee is who owns it at the moment, not where it is in the workflow.
If you insist on doing this, then you will need to find/write a listener that can spot "assignee changed to empty" and trigger a transition from <any status> back into Open. You'll need to change your workflow to include the required transition(s) as well.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs