You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Gilad Shtern If you there are only few dashboards, I would suggest to migrate them manually
1. Create a dashboard on target Jira instance
2. Create a filters on target Jira instance if any gadget on the dashboard using filters to display the results.
3. Update the dashboard permissions/share.
Another way is using the migration plugins as mentioned by Joshua one is https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira other is https://marketplace.atlassian.com/apps/1211147/project-configurator-for-jira?hosting=server&tab=overview
I have a past experience with Configuration manager for Jira.
This plugin allows you to custom select dashboards, filters and boards.
For the dashboard migration you need to select the related filters in import and this will also create the users if they are not already on target server, there are many things you need to review before migrating this using the plugin.
You will require this plugin on both test and prod instance. you can evaluate the plugin on test instance and the decide which approach you like to go with.
There are two options; manually or using a plugin. Manual is exactly what it sounds like, just make them again in the other server. Plugins, such as Project Configurator or Configuration Manager, have the ability to export/import filters and dashboards. They may error if there are database inconsistencies or items are missing; e.g. a dashboard references a filter that was deleted. The plugins may also have reduced functionality if using a trial license, but I'm not sure. Cheers!