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

Custom Fields with same names in team-managed projects not populating data when exporting

    • Severity 3 - Minor

      Issue Summary

      Custom Fields with same names in team-managed (formerly known as next-gen) projects not populating data when exporting when we use open in Microsoft Excel (or Google sheets)option

      Steps to Reproduce

      1. Step 1: Create custom fields with same name in multiple team-managed projects
      2. Step 2: Populate the custom fields by creating tickets in team-managed projects
      3. Step 3: Run an advanced issue search and the Custom Field in the column
      4. Step 4: click on open in Microsoft Excel (or Google sheets) option

      Expected Results

      The exported excel sheet should contain the data for the Custom Field

      Actual Results

      Custom Field data in the exported excel sheet is empty.

      Workaround

      Option 1

      Use the Export to CSV option

      Option 2

      Consider renaming the custom field

      Option 3

      Import issues using Jira Cloud for Excel add-in or Jira Cloud for Sheets app. Both allow you to specify the exact field you are using on your project.

        1. 1.png
          1.png
          66 kB
        2. 2.png
          2.png
          56 kB
        3. 3.png
          3.png
          212 kB
        4. 4.png
          4.png
          19 kB
        5. 5.png
          5.png
          82 kB

            [API-299] Custom Fields with same names in team-managed projects not populating data when exporting

            Rahul made changes -
            Description Original: h3. Issue Summary

            Custom Fields with same names in team-managed (formerly known as next-gen) projects not populating data when exporting when we use *open in Microsoft Excel* option

            h3. Steps to Reproduce
             # Step 1: Create custom fields with same name in multiple team-managed projects
             # Step 2: Populate the custom fields by creating tickets in team-managed projects
             # Step 3: Run an advanced issue search and the Custom Field in the column
             # Step 4: click on *open in Microsoft Excel* option

            h3. Expected Results

            The exported excel sheet should contain the data for the Custom Field
            h3. Actual Results

            Custom Field data in the exported excel sheet is empty.
            h3. Workaround
            h4. Option 1

            Use the Export to CSV option
            h4. Option 2

            Consider renaming the custom field
            h4. Option 3

            Import issues using [Jira Cloud for Excel|https://appsource.microsoft.com/en-us/product/office/WA200000556] add-in or [Jira Cloud for Sheets app|https://marketplace.atlassian.com/apps/1220382/jira-cloud-for-google-sheets-official?tab=overview]. Both allow you to specify the exact field you are using on your project.
            New: h3. Issue Summary

            Custom Fields with same names in team-managed (formerly known as next-gen) projects not populating data when exporting when we use *open in Microsoft Excel* (or Google sheets)option
            h3. Steps to Reproduce
             # Step 1: Create custom fields with same name in multiple team-managed projects
             # Step 2: Populate the custom fields by creating tickets in team-managed projects
             # Step 3: Run an advanced issue search and the Custom Field in the column
             # Step 4: click on *open in Microsoft Excel* (or Google sheets) option

            h3. Expected Results

            The exported excel sheet should contain the data for the Custom Field
            h3. Actual Results

            Custom Field data in the exported excel sheet is empty.
            h3. Workaround
            h4. Option 1

            Use the Export to CSV option
            h4. Option 2

            Consider renaming the custom field
            h4. Option 3

            Import issues using [Jira Cloud for Excel|https://appsource.microsoft.com/en-us/product/office/WA200000556] add-in or [Jira Cloud for Sheets app|https://marketplace.atlassian.com/apps/1220382/jira-cloud-for-google-sheets-official?tab=overview]. Both allow you to specify the exact field you are using on your project.
            Vittal Krishna made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 992012 ]
            Rahul Kumar made changes -
            Component/s New: Jira Cloud for Google Sheets [ 55791 ]
            Max made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 820113 ]
            Vitalii Saienko (Inactive) made changes -
            Link New: This issue causes JRACLOUD-81312 [ JRACLOUD-81312 ]
            Abhishek Singh made changes -
            Labels New: jsm-s16
            K. Yamamoto made changes -
            Link New: This issue is related to JRACLOUD-77919 [ JRACLOUD-77919 ]
            Niel Del Rosario made changes -
            Description Original: h3. Issue Summary

            Custom Fields with same names in next-gen projects not populating data when exporting when we use *open in Microsoft Excel* option
            h3. Steps to Reproduce
             # Step 1: Create custom fields with same name in multiple next-gen projects
             # Step 2: Populate the custom fields by creating tickets in next-gen projects
             # Step 3: Run an advanced issue search and the Custom Field in the column
             # Step 4: click on *open in Microsoft Excel* option

            h3. Expected Results

            The exported excel sheet should contain the data for the Custom Field
            h3. Actual Results

            Custom Field data in the exported excel sheet is empty.
            h3. Workaround
            h4. Option 1

            Use the Export to CSV option
            h4. Option 2

            Consider renaming the custom field
            h4. Option 3

            Import issues using [Jira Cloud for Excel|https://appsource.microsoft.com/en-us/product/office/WA200000556] add-in or [Jira Cloud for Sheets app|https://marketplace.atlassian.com/apps/1220382/jira-cloud-for-google-sheets-official?tab=overview]. Both allow you to specify the exact field you are using on your project.
            New: h3. Issue Summary

            Custom Fields with same names in team-managed (formerly known as next-gen) projects not populating data when exporting when we use *open in Microsoft Excel* option

            h3. Steps to Reproduce
             # Step 1: Create custom fields with same name in multiple team-managed projects
             # Step 2: Populate the custom fields by creating tickets in team-managed projects
             # Step 3: Run an advanced issue search and the Custom Field in the column
             # Step 4: click on *open in Microsoft Excel* option

            h3. Expected Results

            The exported excel sheet should contain the data for the Custom Field
            h3. Actual Results

            Custom Field data in the exported excel sheet is empty.
            h3. Workaround
            h4. Option 1

            Use the Export to CSV option
            h4. Option 2

            Consider renaming the custom field
            h4. Option 3

            Import issues using [Jira Cloud for Excel|https://appsource.microsoft.com/en-us/product/office/WA200000556] add-in or [Jira Cloud for Sheets app|https://marketplace.atlassian.com/apps/1220382/jira-cloud-for-google-sheets-official?tab=overview]. Both allow you to specify the exact field you are using on your project.
            Niel Del Rosario made changes -
            Summary Original: Custom Fields with same names in next-gen projects not populating data when exporting New: Custom Fields with same names in team-managed projects not populating data when exporting
            Vitalii Saienko (Inactive) made changes -
            Description Original: h3. Issue Summary

            Custom Fields with same names in next-gen projects not populating data when exporting when we use *open in Microsoft Excel* option

            h3. Steps to Reproduce
             # Step 1: Create custom fields with same name in multiple next-gen projects
             # Step 2: Populate the custom fields by creating tickets in next-gen projects
             # Step 3: Run an advanced issue search and the Custom Field in the column
             # Step 4: click on *open in Microsoft Excel* option


            h3. Expected Results

            The exported excel sheet should contain the data for the Custom Field

            h3. Actual Results

            Custom Field data in the exported excel sheet is empty.


            h3. Workaround

            Use the Export to CSV option or you could also consider renaming the custom field
            New: h3. Issue Summary

            Custom Fields with same names in next-gen projects not populating data when exporting when we use *open in Microsoft Excel* option
            h3. Steps to Reproduce
             # Step 1: Create custom fields with same name in multiple next-gen projects
             # Step 2: Populate the custom fields by creating tickets in next-gen projects
             # Step 3: Run an advanced issue search and the Custom Field in the column
             # Step 4: click on *open in Microsoft Excel* option

            h3. Expected Results

            The exported excel sheet should contain the data for the Custom Field
            h3. Actual Results

            Custom Field data in the exported excel sheet is empty.
            h3. Workaround
            h4. Option 1

            Use the Export to CSV option
            h4. Option 2

            Consider renaming the custom field
            h4. Option 3

            Import issues using [Jira Cloud for Excel|https://appsource.microsoft.com/en-us/product/office/WA200000556] add-in or [Jira Cloud for Sheets app|https://marketplace.atlassian.com/apps/1220382/jira-cloud-for-google-sheets-official?tab=overview]. Both allow you to specify the exact field you are using on your project.

              Unassigned Unassigned
              vrai@atlassian.com VR
              Affected customers:
              37 This affects my team
              Watchers:
              68 Start watching this issue

                Created:
                Updated: