We have an actual JIRA production instance that carried out few project, and we want to move out a specific project to its own JIRA instance.
After restoring a database backup to the new database along with the matching archive data from he JIRA home directory source instance (data/attachments, data/avatars, caches, plugins) to the new instance, removing all non necessary projects using JIRA UI with Administration - PROJECT - delete is the best way to achieve that ?
What about the other JIRA objects such as components, versions, workflows, workflow scheme, issue type, issue type scheme, permissions, etc..., can those be remove safely as well using the JIRA UI ?
In what order the removal should be done ( project first then the object or the other way around )?
It seems to still have remaining project entries in the data/attachments for a project that has been removed, can I just delete those at OS level (rm -fr /home/jira/data/attachments/PRJ_ID) ?
Does the complete process can be done from the command-line using api calls ?
Using "delete project" in the UI is the best approach, yes. That will kill off components and versions, but not the shared scheme settings. However, any schemes that end up as redundant will show as "inactive" or not associated with any projects in the lists of schemes, and that will show you what is safe to delete manually.
You have to do the projects first - some config cannot be deleted while it is still associated with a project.
The process should delete the attachments for you too.
Finally, no, the REST API does not expose the admin functions you need to delete this stuff!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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