Moving 'Done' issues to another project

[Charley Buck]

We have a problem within multiple projects, where there are just too many 'Done' epics and issues clogging up the project in the background.

We'd like to have a system in place whereby once an issue or epic is 'Done', it then gets moved to an archive project we have created. 

While I understand that issues belong to projects rather than boards or company licenses, surely there is a way to automate the process of moving issues from one project to another? And if there isn't then surely this should be explored?

TIA!

[Sayed Bares _ServiceRocket_]

As @John Funk mentioned it would be way better if you exclude done epics from your board. However, if you still want to move your issue then what you could do instead is cloning your issue (Clone issue) first and then deleting your issue (Delete issue) from original project. It is not an exact move action but it can be used as a workaround.

[John Funk]

I would discourage deleting issues. They can be closed out, but I don't think it is a good idea to delete them. 

[John Funk]

Hi Charley - Welcome to the Atlassian Community!

No, there is no automation that exists that can do a Move. There is too much going on behind the scenes, and I would not bet on it happening in my lifetime even if a good idea. 

So the next focus is to ask why it is "clogging up the project"? In what way is it clogging it up in the background? Why not just adjust the filter for your board to not include Epics that are Done?