-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
6.3.4
-
6.03
-
3
-
Severity 3 - Minor
-
2
-
Index may cause issue during CSV import. It happens when there is project with single issue type only and there is required custom field with Context set to that project. During manual creation is everything OK.
Replication
- Create new JIRA project, with exactly one issue type.
- Add new custom field. And restrict context for that issue type.
- In project Issue Field Configuration scheme set all fields to optional, except Sumary (It is mandatory to have it mandatory) and the new custom field.
- Create issue normally - it works
- Create issue by CSV import - Import fails because that field is always treated as null.
Note: Because there is only single issue type, import wizard do not offer Issue Type for mapping. My theory is that importer checks context before it actually applies issue type - automatically.
Workaround: Set context into project instead of Issue type.
- was cloned as
-
JIM-1528 Failed to load
6.4.6 is affected as well. When utilizing the import option from Issues -> Import Issues from CSV, the following fields that it errors out on are present in the CSV, but when validating or attempting to import, I get the following errors:
The value [
{null=Regression} ] can't be added to the Custom Field [ Bug Type ]. The value [ {null=Regression}] can't be found or is in the incorrect format
and
The validation process has found 1 error/s
Issue can't be created due to the error/s [ Affects Version/s is required.; Bug Type is required. ]
Bug Type and Affects Version/s field are required.