Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-84872

Issue Search should export Parent field values as the Issue Key

XMLWordPrintable

    • 4

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      Previously, Epic Link field for issues would contain the value of the Issue Key:

      Issue Key Epic Link Summary
      ABC-123 ABC-111 "Child summary"

      After the change: Upcoming changes: 'epic-link' replaced with 'parent', exporting the same data is not possible because the Epic Link field is no longer used. The user likely sees the message: "Epic Link will soon be replaced with Parent. Use the Parent field instead"

      Users need to rely on the Parent field:

      Issue Key Parent Summary
      ABC-123 12345 "Child summary"

      In this example, the value 12345 represents the Issue Id of the Parent (ABC-111). However, the exported data is not user-friendly as it relies on the user to remap the issue key value or export more data from Jira.

      Suggestion

      It would be helpful if users could select an option to translate the issue ID to the Issue Key value. When exporting, users may need to visualize the referenced data easily.

      An import might not be in scope, therefore, it would be helpful to allow the user to determine how the Parent field value is displayed for the exported CSV.

              Unassigned Unassigned
              asalinasii@atlassian.com Alfonso S. [Atlassian Support]
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: