I want to migrate Dashboards and filters from one JIRA instance to another. We can't realize the system restore because it'll wipe out all the target JIRA content.
How can I do it without recreating manually all the Dashboards? There are like 50 Dashboards and filters.
Thank you so much in advance.
Looks like our add-on - Configuration Manager for JIRA - will be well suited for this job. It has support for filters and support for dashboards will be available very soon (including resolution of referenced configuration objects in queries and gadgets for proper handling).
If you'd like an online demo or have further questions don't hesitate to drop us an email at firstname.lastname@example.org.
We are using your plugin "Configuration Manager for JIRA" to export and import configurations between two JIRA instances. The target instance already contains projects, so we cannot restore system from the old instance backup. We can only use the import project to import data from the old to the target instance.
We are more than satisfied with the results given with your plugin, but now we need to import dashboards and filters and apparently the current plugin version does not offer this possibility.
Please, is there any way we can export and import all the dashboards and filters defined in the old instance without restoring the old instance backup and without doing it manually?
Thank you so much in advance for your help.
We're very happy that you like the add-on, thank you!
CMJ does support filters – you can select the filters you want to migrate (or select all) when creating a project snapshot - https://botronsoft.atlassian.net/wiki/display/CMJ/Filters. In your case the best way to do it is to create a snapshot of a simple project (that already exists on the target JIRA or it will be deleted after the deployment) and select all the filters that need to be moved in the snapshot creation wizard.
As for dashboards – we’re currently working very hard to add support for dashboards and include proper reference handling for as many gadgets as we can for the first version of the feature. We expect to release this feature in about a month.
Having taken this approach once, I do not recommend merging data from one JIRA database to another. The ids will all need updating, then then foreign keys, then the sequence table. The main table for filters has references to sharing tables by group, project etc. It's all better done at the application level.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot