-
Bug
-
Resolution: Fixed
-
Medium
-
6.0.27
-
None
If you have a CSV file that uses the "Epic Name" field (for example) associated to issues that are not type Epic, when the CSV file is imported to JIRA, the context of the "Epic Name" field will be changed.
Attached file as an example for import
- relates to
-
JRASERVER-67230 JIRA External System Import (JIM) can create new options for locked custom fields
-
- Gathering Impact
-
[JIM-1089] Import from Comma-separated values (CSV) fails to validate Epic fields
Link | New: This issue relates to JRASERVER-67230 [ JRASERVER-67230 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Workflow | Original: JIM Project Workflow (Software Simplified) [ 1607228 ] | New: JIM - workflow v2 [ 1611529 ] |