-
Bug
-
Resolution: Timed out
-
Medium
-
8
-
Severity 3 - Minor
-
0
-
Summary
Unable to download json detailed log if the json file contain invalid format
Steps to Reproduce
Export any Jira issue in json format and edit the due date format (see below):
"duedate": ",\"",
Actual Result
It redirects to https://<Cloud URL>.atlassian.net/rest/jira-importers-plugin/1.0/importer/com.atlassian.jira.plugins.jim-plugin:jsonImporter/log with below error message:
This <Cloud URL>.atlassian.net page can’t be found It may have been moved or deleted. HTTP ERROR 410
Expected Result
The log should be downloaded.
Stack Trace
msg: There was a problem validating the json file. The fields [issues, duedate] are not valid.
stack: java.lang.RuntimeException: There was a problem validating the json file. The fields [issues, duedate] are not valid.
at com.atlassian.jira.plugins.importer.sample.SampleDataImporterImpl.parseSampleData(SampleDataImporterImpl.java:71)
at com.atlassian.jira.plugins.importer.imports.taskrunners.JsonImporterTaskRunner.createDataBean(JsonImporterTaskRunner.java:85)
[JRACLOUD-81927] Unable to download json detailed log if there is invalid format
Hello!
We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.
Survey link - https://forms.gle/NYNkmS92r96z42QV9
Thanks!
Prashanth M
Product Manager, Jira Platform
I'm also getting bit by this. Kind of hard to figure out what field or values it's angered at when you can't access the log.
Just ran into this.. trying to import 1 issue and the import failed due to a "bad attachment". Not even sure what that was, but cannot tell since the domain "can't be found".
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team