Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-19863

Support the importing of "Epic Link" with "Epic Name"

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Epics
    • None
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, the only way to link issues to Epics via the CSV import is to map the "Epic Link" field to the issue key of the Epic.

      That being the case, in order to import Epics and linked issues on the same CSV file, we need to manually set an "Issue Key" for the Epics, requiring us to know of a unique "Issue Key" that can be used and making it only possible to achieve this using the External System Import tool, only available to administrators.

      It should be possible to either use the same principles available for linking issues - assigning an ID exclusive to that project and linking issues via that value; or allowing the linkage using "Epic Name".

            [JSWSERVER-19863] Support the importing of "Epic Link" with "Epic Name"

            There are no comments yet on this issue.

              Unassigned Unassigned
              jpalharini Joao Palharini (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: