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

JIRA Issue Navigator Export CSV Current Fields

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Reports
    • 1
    • 5
    • 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.

      I noticed this week after a JIRA upgrade that the issue navigator export to CSV current fields changed the data being exported. We just moved to 7.3 on Tuesday night. Before the change the assignee was the full name of the resource and the epic link was the name given to the epic link. After the change the assignee now uses the username and the epic link uses JIRA number assigned.

      For example:
      Before:

      Assignee – Bill Smith
      Epic Link – Vendor Files

      After:

      Assignee – bsmith
      Epic Link – ETLENCSCRU – 7

      How do I get the original values from the before example?

            [JSWSERVER-15572] JIRA Issue Navigator Export CSV Current Fields

            felipe.amaral added a comment -

            Please implement the requested change. There is a lot of value in being able to see the name of the epic when reviewing reports. The epic issue key adds zero value as it isn't useful for reporting.

            felipe.amaral added a comment - Please implement the requested change. There is a lot of value in being able to see the name of the epic when reviewing reports. The epic issue key adds zero value as it isn't useful for reporting.

            Debbie Munson added a comment -

            Relevant ticket about the need to have the Epic Name in issue exports here

            https://jira.atlassian.com/browse/JRACLOUD-78582

            Debbie Munson added a comment - Relevant ticket about the need to have the Epic Name in issue exports here https://jira.atlassian.com/browse/JRACLOUD-78582

            Kate Nevenchannaya added a comment -

            At Adobe, we get more and more complaints from users regarding this, due to export results being less readable (and less useful) than expected and than they used to be. Thanks for considering!

            Kate Nevenchannaya added a comment - At Adobe, we get more and more complaints from users regarding this, due to export results being less readable (and less useful) than expected and than they used to be. Thanks for considering!

            Dario B added a comment - - edited

            This is related to the bug tracked in JSWSERVER-14746.

            Dario B added a comment - - edited This is related to the bug tracked in JSWSERVER-14746 .

              9dec92182c8f AviGhosh
              b689eed21802 Lou Pietrocarlo
              Votes:
              18 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: