Effect of restoring a project

[aaron_simon]

Hi there,

I'm looking for the following information:

• What happens to Jira issues after an archived Project is restored?
• If tickets had been moved out of that Project prior to it being archived into a new project, will those issues be changed after the Project is restored?

Details follow:

My organization recently reorganized and consolidated our Jira projects. After a review of our work, we decided to consolidate six Projects into one, move the open tickets from those six Projects into a new Project, and then archive the old Projects. The archive process worked fine, but we're now in a position where some of our engineers are hoping to refer to some of their past work and refresh our documentation. The catch is, because one cannot search through archived issues, and it appears that archived Epics lose associations to each other and their child issues, the only way to go about referring to those issues is by restoring the project.

While that is a possibility, I want to know if doing so will mess up or change anything in the new project, or if they should remain untouched. I'm also curious about what we're seeing with relationships between issues appearing to be broken. (E.g., we had several issues in an epic, all with names like "Step 1.1.2" and "Step 1.1.3." After looking at that epic in the archive, none of the issues appear as child issues.)

Thanks!

[Jack Brickey · Accepted solution]

Hi @aaron_simon , welcome to the Community.

Archiving more or less just hides a project. So whatever issues existed in the project at the time of archiving will exist when restored nothing more nothing less.