Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-35644

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

XMLWordPrintable

      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

        1. csv_agile.csv
          2 kB

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

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.02
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2839700 ] New: JAC Bug Workflow v3 [ 2917474 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2569884 ] New: JAC Bug Workflow v2 [ 2839700 ]
            Tim Evans (Inactive) made changes -
            Link New: This issue relates to JRASERVER-67230 [ JRASERVER-67230 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1536743 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2569884 ]
            jonah (Inactive) made changes -
            Description Original: 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             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-35644].
              {panel}

            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
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-35644 [ JRACLOUD-35644 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-cloud New: affects-cloud affects-server
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-cloud
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 679571 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1536743 ]

              Unassigned Unassigned
              cgauterio Clarissa Gauterio (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: