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
The JCMA does not migrate
Boards not connected to the projects being migrated
Boards that belong to inactive users
filters on boards that are not migrated
What's the best way to migrate these, given that site import has been deprecated and it's not possible?
Outside of using the JCMA dark features (which currently have a bug that requires a downgrade to 1.6.5) what is the best way to get this done in a way that preserves ownership, shares, subscriptions, etc? How do you ensure nothing is missed?
I've been following other posts here and in other forums, and I'm not seeing a lot of answers.
This topic indeed deserves more documentation on how to approach this.
I had following solution for
Boards, filters and dashboards from inactive users can be listed with a database sql query.
This is a very time consuming proces but it leads to a clean Jira instance.
Thanks @Erik Mathijs ,
Certainly, migration is the perfect opportunity for cleanup, but in the end there's still going to be a lot to move.
It's been my experience that more often than not, shared objects created by inactive users are still very much in use.
The solution you have addresses clutter, but once the decluttering is done, how are they moved?
The cleanup is essential for me, so i did this (hel of a job ;) ).
I am aware that filters and cross-project boards will not be converted.
My plan is that during user acceptance testing, each user creates his (or her) filters and dashboards.
cross-project boards must also be created by the teams
All users are getting a list of their shared objects, wich must be (unfortunately) created again.
At the end of user acceptance testing, each user and each team must be aware of the actions they have to do for starting in cloud.
Despite this approach, I regret that certain shared objects are not migrated.
I understand this for Dashboards, because they can have many gadgets, but migrating filters should be less effort to built in the JMMA (from my point of view).
Another action i put on the admin list is to keep our jira instance clean (also after migration to cloud).
So before deactivating a jira user
- all shared objects must be transferred to a active user.
- private objects will be deleted
For this task we use the Adaptavist Scriptrunner
I hope you can do something with my experience.
Questions or comments are of course welcome because I may be able to adjust my approach here
Thanks Erik - I really appreciate the information, and its very helpful, but it also assumes that the users are going to take action.
Let's assume that's not the case, and a single internal admin or 3rd party, such as a solution partner, is taking on that work. How is it all done then? That's the heart of my question.
As far as I can tell, that person will need to manually inventory each object, document all of its properties (owner, JQL, shares, configurations, etc), and then manually recreate them all, one by one, in the cloud site.
I wish you al the best with your migration to cloud. I know the feeling because i'm also working on it for our company.
I'm asking both because I want to know, and because this is a HUGE risk for organizations, and a huge gap in the documentation. I can't find anything other than the "what's not migrated with the JCMA" blurb that even hints at this.
There should be full articles dedicated to this topic.