[JRASERVER-35644] Import from Comma-separated values (CSV) fails to validate Epic fields

Type: Bug
Resolution: Fixed
Priority: Medium (View bug fix roadmap)
Fix Version/s: 6.1.6
Affects Version/s: 6.2-OD-1
Component/s: Import / Export [Deprecated]
Labels:
- affects-cloud
- affects-server

Introduced in Version:
6.02
Bug Fix Policy:
View Atlassian Server bug fix policy

NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

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

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

csv_agile.csv
2 kB
04/Nov/2013 8:06 PM

causes

JSWSERVER-9552 Incorrect contexts for Epic related fields

Closed

is related to

JSWSERVER-8769 Duplicate Custom Fields created as part of a GreenHopper upgrade

Closed

relates to

JRACLOUD-35644 Import from Comma-separated values (CSV) fails to validate Epic fields

Closed

JRASERVER-67230 JIRA External System Import (JIM) can create new options for locked custom fields

Gathering Impact

was cloned as: JIM-1089 Failed to load

There are no comments yet on this issue.

Assignee:: Unassigned

Reporter:: Clarissa Gauterio (Inactive)

Affected customers:: 0 This affects my team

Watchers:: 6 Start watching this issue

Created:: 04/Nov/2013 8:06 PM

Updated:: 28/Mar/2019 12:12 AM

Resolved:: 10/Mar/2014 8:05 AM

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates