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

Epic Name field is empty when exporting issues to Excel CSV format

       

      Update - Apr 6th 2019

      Hi everyone,

      This is indeed not a bug but an expected behavior. The reason is:

      • Epic Name is specific to Epic issue type
      • Epic Link is used by other issue types to link to an Epic issue type

      So basically:

      • An Epic has Epic Name but no Epic Link
      • Other issue types can have an Epic Link but can never have an Epic Name - this is the reason why the Epic Name column is empty for non-Epic issue types

      Please refer to JSWSERVER-15878 for more details and watch it for a more suitable solution.

      Original Description

      Summary

      When exporting issues that are part of an Epic using the Excel CSV export option, the Epic Name field is not exported at all

      Steps to Reproduce

      1. Create an Epic
      2. Create several new issues under this new Epic
      3. Export the issues to Excel CSV

      Expected Results

      Issues should be exported with the Epic Name being displayed

      Actual Results

      The Epic Name column is completely empty

      Workaround

      No workaround

       

            [JSWSERVER-14746] Epic Name field is empty when exporting issues to Excel CSV format

            Zac Xu made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 492824 ]
            Andy Nguyen (Inactive) made changes -
            Link New: This issue is superseded by JSWSERVER-15878 [ JSWSERVER-15878 ]
            Andy Nguyen (Inactive) made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Andy Nguyen (Inactive) made changes -
            Description Original: h3. Summary
            When exporting issues that are part of an Epic using the Excel CSV export option, the Epic Name field is not exported at all


            h3. Steps to Reproduce
            # Create an Epic
            # Create several new issues under this new Epic
            # Export the issues to Excel CSV

            h3. Expected Results
            Issues should be exported with the Epic Name being displayed

            h3. Actual Results
            The Epic Name column is completely empty
             
            h3.Workaround
            No workaround
            New:  
            {panel:title=Update - Apr 6th 2019}
            Hi everyone,

            This is indeed not a bug but an expected behavior. The reason is:
             * Epic Name is specific to Epic issue type
             * Epic Link is used by other issue types to link to an Epic issue type

            So basically:
             * An Epic has Epic Name but no Epic Link
             * Other issue types can have an Epic Link but can never have an Epic Name - this is the reason why the Epic Name column is empty for non-Epic issue types

            Please refer to JSWSERVER-15878 for more details and watch it for a more suitable solution.
            {panel}
            {panel:title=Original Description}
            h3. Summary

            When exporting issues that are part of an Epic using the Excel CSV export option, the Epic Name field is not exported at all
            h3. Steps to Reproduce
             # Create an Epic
             # Create several new issues under this new Epic
             # Export the issues to Excel CSV

            h3. Expected Results

            Issues should be exported with the Epic Name being displayed
            h3. Actual Results

            The Epic Name column is completely empty
            h3. Workaround

            No workaround
            {panel}
             
            SET Analytics Bot made changes -
            UIS Original: 39 New: 64
            Bugfix Automation Bot made changes -
            Support reference count Original: 24 New: 25
            Bugfix Automation Bot made changes -
            Minimum Version New: 7.02
            SET Analytics Bot made changes -
            UIS Original: 41 New: 39
            SET Analytics Bot made changes -
            UIS Original: 37 New: 41
            SET Analytics Bot made changes -
            UIS Original: 43 New: 37

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Affected customers:
              79 This affects my team
              Watchers:
              81 Start watching this issue

                Created:
                Updated:
                Resolved: