Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-488

Exporting issues using 'Open in Microsoft Excel' feature does not export Team-managed custom fields values

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • None
    • Jira Cloud for Excel
    • None
    • Severity 3 - Minor

      Issue Summary

      Exporting issues using the 'Open in Microsoft Excel' feature does not export Team-managed custom fields values.

      Steps to Reproduce

      1. Create the same custom field name in more than one Team Managed project
      2. Search for issues from team-managed projects that have custom fields created and populated.
      3. Export the issues using the 'Open in Microsoft Excel' feature.
      4. Custom fields from the Team-managed project will be empty and lack data.

      Expected Results

      Excel file should contain Team-managed custom field data.

      Actual Results

      Excel file does not contain Team-managed custom field data.

      Workaround

      Export issues using Export Excel CSV (All fields)/(Current field) feature.
      Or
      From Google sheet Get issues from Jira and select the correct custom field

        1. Data retrieved for the correct custom field.png
          Data retrieved for the correct custom field.png
          35 kB
        2. How to reproducce the problem.mov
          11.57 MB
        3. screenshot-1.png
          screenshot-1.png
          21 kB
        4. workaround in google sheet.mov
          3.20 MB

            [API-488] Exporting issues using 'Open in Microsoft Excel' feature does not export Team-managed custom fields values

            Vitalii Saienko (Inactive) added a comment -

            Closing this as duplicate. Please follow updates here https://jira.atlassian.com/browse/API-299

            Vitalii Saienko (Inactive) added a comment - Closing this as duplicate. Please follow updates here https://jira.atlassian.com/browse/API-299

            Vitalii Saienko (Inactive) added a comment -

            Hi 30a8eb7ed6bb

            I'm one of the developers of the "Open in Excel/Sheets" functionality. I was reading through the original support ticket and I have an idea. Since you experience this problem with the team-managed project, it might be that another team-managed project has a custom field with the same name. We had this problem several times in the past.

            May I ask you to open the problematic filter, click on the "Columns" and type the name of the field? Do you see only one field with that name or several fields? If several, enable another one and try to export the data again using the "Open in Excel" button.

            Let me know if that worked.

            Vitalii Saienko (Inactive) added a comment - Hi 30a8eb7ed6bb I'm one of the developers of the "Open in Excel/Sheets" functionality. I was reading through the original support ticket and I have an idea. Since you experience this problem with the team-managed project, it might be that another team-managed project has a custom field with the same name. We had this problem several times in the past. May I ask you to open the problematic filter, click on the "Columns" and type the name of the field? Do you see only one field with that name or several fields? If several, enable another one and try to export the data again using the "Open in Excel" button. Let me know if that worked.

              Unassigned Unassigned
              023fbc695e10 Vasilije Dramicanin
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: