Uploaded image for project: 'JIRA Importers Plugin'
  1. JIRA Importers Plugin
  2. JIM-1089

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

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 6.0.29
    • 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

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

            Przemyslaw Borkowski (Inactive) added a comment - - edited

            Oswaldo Hernandez, JIM 6.0.29 is in JIRA master & stable (QA took some time) - We will try to do it faster with 6.0.30

            Przemyslaw Borkowski (Inactive) added a comment - - edited Oswaldo Hernandez, JIM 6.0.29 is in JIRA master & stable (QA took some time) - We will try to do it faster with 6.0.30

            Przemyslaw Borkowski (Inactive) added a comment -

            Fixed - JIM will no longer add IssueTypes to Locked Custom Fields

            Przemyslaw Borkowski (Inactive) added a comment - Fixed - JIM will no longer add IssueTypes to Locked Custom Fields

              Unassigned Unassigned
              Anonymous Anonymous
              Archiver:
              dnorton@atlassian.com Dave Norton

                Created:
                Updated:
                Resolved:
                Archived: