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
We are evaluating migration of our Server Jira installation to the cloud.
On one of the projects, migration fails on importing the Board of the project.
Error on the log is as shown below:
2020-05-26 18:59:19.252 ERROR KP project-import We couldn't import Board 'Kickbox board'. Reason: query: The value '1.40.0' does not exist for the field 'fixVersion'.. This caused 47341 other items to fail.
The value '1.40.0' is used on several issues as Fix Version value, also the swimlanes looks like working correctly in the Server installation.
The first thing I would check is the exact spelling of 1.40.0 in all instances as it is very easy to have something which looks like that but is actually different. Versions are just a text string and can be different without looking so....
may all appear the same but are very different with O and 0. But the one that often catches people out is where there is a trailing space.
Once you have checked all these then I would make sure with a single issue import that the layout of the item in your import file does not contain any spurious characters (tabs, non-printing spaces, etc)
Hope this helps you to troubleshoot a bit further.
It will be kind of difficult to import a single issue, as we are using the "Jira Cloud Migration Assistant" from the available app list in jira, which only supports migration of full projects.
The swimlanes are configured on the board to be based on queries, where the Fixversion is defined. The editor there is automatically adding a space after the number, when entering, as it is expecting something like AND/OR/etc.. Strange thing is that the swimlanes on the board do function correctly with the defined queries.
For now, removed the trailing space, and trying again.. And know what? It works.. But, not because of my change.. There was an update on the app.. As, before updating the board, a copy was made.. And, forgot to update that one.. Arrghhh. Thanks anyway...
Well I am glad you have solved your problem it is amazing how often we can come across things that work when tried just one more time. Also do not expect consistency is something I learnt a long time ago with software written by different folk. One might remember to trim a string to remove trailing spaces whilst another might not and as the testers might also be different people/time they may not even pick up this subtle difference.