Not directly. The sticking point for me is trapping the user who does the move when they do it - once you've stored that, assigning back to it on closing the issue should not be hard with Automation or the Script Runner.
On server, I know I can write a listener with the Script Runner to catch the move event and update. I've not tried it with Cloud Script Runner.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events