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

Importing epics via CSV Importer could be improved

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Icon: Medium Medium
    • 6.1.12
    • 6.1.5
    • CSV
    • None

      A comment from JIM-988

      I've done some testing and came to the conclusion that epic linkage does not work if there's more than one epic with the same name in the system.
      For example, let's say there's an epic with epic name "MyEpic" in an existing project. If I try to do a csv import into a new project with data containing an epic named "MyEpic" and a story with epic linkage "MyEpic", I will get the error "Cannot add value [ MyEpic] to CustomField Epic Link in Issue AAA-XXX. Probably value was in incorrect format".
      So not only is the error message misleading but once again the problem with Jira handling Epics as globals come into play.
      Since I choose what project to import my csv into it would make sense that Jira looks into that project only.
      Another problem is that in my csv, the epics need to be imported before the stories, otherwise I get the same error. Michal Kujalowicz latest comment suggests this should not be a problem ("Epics are imported in the first step and then next issues are properly linked to them.").

            [JIM-1269] Importing epics via CSV Importer could be improved

            StanislavA added a comment -

            There was extended search algorithm, which resolves epic issue for epic link:

            1. epic link is consider to be issue key, or
            2. epic link is consider to be epic name of an epic, which is inside the same project as the epic story, which defines epic link, or
            3. epic link is consider to be epic name of an epic, which is defined in some project (it has to be unique epic name over all projects, if it want to be resolved) - it is because of back compatibility

            Tested:
            It was tested by integration test:
            it.com.atlassian.jira.webtest.selenium.admin.imports.csv.TestCsvCustomFields.testGHEpicImport()

            for next scenarios:

            1. epic link is to epic defined by issue key
            2. epic link is to epic defined by epic name and is in a same project as a epic story
            3. epic link is to epic defined by epic name which is in different project as a epic story

            StanislavA added a comment - There was extended search algorithm, which resolves epic issue for epic link: epic link is consider to be issue key, or epic link is consider to be epic name of an epic, which is inside the same project as the epic story, which defines epic link, or epic link is consider to be epic name of an epic, which is defined in some project (it has to be unique epic name over all projects, if it want to be resolved) - it is because of back compatibility Tested: It was tested by integration test: it.com.atlassian.jira.webtest.selenium.admin.imports.csv.TestCsvCustomFields.testGHEpicImport() for next scenarios: epic link is to epic defined by issue key epic link is to epic defined by epic name and is in a same project as a epic story epic link is to epic defined by epic name which is in different project as a epic story

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

                Created:
                Updated:
                Resolved:
                Archived: