-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
1
-
Hi all,
I had recently to use project import and during the import from ZIP file I experienced the following error.
There was a problem parsing the backup XML file at /var/atlassian*....zip. No 'issue' field for CustomFieldValue 'xxxxx'.
I managed to edit entries.xml in the ZIP and remove node CustomFieldValue which had not attribue issue. Actually there were two instances - the import failed on the first one. After save and zipping, import accepted the new ZIP file and my data were restored.
My queestion is why the "Integrity Checker" doesn't cover such cases? I personally see it as a pretty severe inconsistency. I was lucky that this happen on non Production instance, where is by the way such invalid record too. I am planning to remove it on prod by executing
DELETE FROM customfieldvalue WHERE issue IS NULL;
It would be really great if you can add the solution I took (unzip, XML edit, save) to your Confluence to help others, of course it's valid and OK .
Optimally add such check to the "Integrity Checker" and let administrators fix it from the UI.
Thank you,
Jaroslav
PS: This doesn't change the fact that JIRA is the best tracking tool I worked with! Good job!
- duplicates
-
JRASERVER-34373 Add check for CustomFieldValue to catch rows where CustomFieldValue contains null ID
- Needs Triage
-
JRASERVER-10816 Improve Integrity checker
- Closed
- relates to
-
JRASERVER-67011 Duplicate value in "Time in Status" Field persists despite fix code in place
- Closed