-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Severity 3 - Minor
-
0
-
Issue Summary
The importer fails when trying to import against a custom field that has multiple issue type scope.
Steps to Reproduce
- Create a custom field (ie. Custom Summary)
- Add a context and restrict it to issue type Bugs
- Add a second context and restrict it to issue type Task
- Import a new Story issue via JSON and populate the Custom Summary field.
Expected Results
The JSON importer should be able to handle the data or error out gracefully specifying which custom field cannot be handled.
ie. Error : Custom Summary is currently not available for issue Type Story.
Actual Results
The importer fails with a vague error and there is no indication which custom field was causing the error
ERROR - Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: expected one element but was: <com.atlassian.jira.issue.fields.config.FieldConfigSchemeImpl@c048c6ab, com.atlassian.jira.issue.fields.config.FieldConfigSchemeImpl@60a994b5>
This gets problematic when there is a huge number of custom fields being imported.
Workaround
Check the custom fields configurations one by one to see which one could be causing the failure.
[JRACLOUD-81961] JSON importer unable to handle a custom field with multiple issue type scopes
Hi Prashanth,
We have a couple thousand projects to import from various other instances into Data Center, and had to give up on JSON as an import option.
While less frequent, today we have the error with CSV.
First, everyone on the team loses an hour waiting for a full reindex to see if that was the issue.
Then the associate performing the problem import loses more hours and even days trying to find the problem field.
If Atlassian could simply note the name of the field(s) in the error message, our time spent debugging this would be reduced by 90%.
Since you asked us to stop using Server and expect us to consolidate on either DC or Cloud, we think getting sufficient information from an error like this is a reasonable ask.
I've submitted your survey as jck0***** at gmail dot com.
Thanks!
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
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