nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project Clean Up: Archiving vs Deleting with a Back-Up

Kavitha Chandrasekaran

Hi All

We are considering two options for Project clean-up.

1) Keeping the Archived project in live instance and grouping those to specific Schemes and Workflows only for Archived projects. Not a real clean-up but gives some sort of organisation/separation of Active and Archived projects.

2) Take a back-up of the instance, delete the Archived projects in the live instance.

If needed, restore the back-Up to a sandbox. We have Enterprise edition allowing for 10 Sandboxes.

In the event a project needs to be restored, export specific projects from Sandbox and import to the Live site.

Anyone see any major issues with the second approach. I think this will be much cleaner and quicker, when you have 200-300 projects Archived and linked to all kinds of Workflows and Workflow Schemes along with Active projects.

Thank You!

Accepted answers

Matteo Vecchiato

Hi @Kavitha Chandrasekaran ,

In my recently experience about moving project between sandbox and production, the copy of project and configuration is not very clean and produce duplication of custom fields, workflows and so on.

If I should take the decision, I would prefer to maintain the project as archived for the required time, and then delete when not required; otherwise, try to use an external tool for backups that offer integration with Atlassian.

I hope it helps

All comments

Matteo Vecchiato

Hi @Kavitha Chandrasekaran ,

In my recently experience about moving project between sandbox and production, the copy of project and configuration is not very clean and produce duplication of custom fields, workflows and so on.

I hope it helps

Carlos Garcia Navarro

Hi @Kavitha Chandrasekaran , It should work, but just to make sure you don't experience issues (like the ones Matteo mentioned), can you run a test and try to import a backup into a sandbox?

https://support.atlassian.com/jira-cloud-administration/docs/export-issues/

Kavitha Chandrasekaran

Thanks much! Yes understand. Don't want to create additional clean-up.

Marc -Devoteam-

Hi @Matteo Vecchiato

I agree whit @Matteo Vecchiato on his concerns.

In my opinion it depends, what is you need to restore, issue information only?

Yes then using a sandbox for restoring can be a simple option to keep your main instance clean, except if you use 3rd party apps that hold crucial information in field etc.. then I would use the archive method.

This related to the concerns of @Matteo Vecchiato

Matteo Vecchiato

Yes @Marc -Devoteam- , the restoration of apps data and copy data from sandbox to production is very challenging.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud