-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
None
-
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
- 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
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.
- causes
-
-
- Closed
-
- is caused by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
JRACLOUD-77919 Exporting issues creates duplicate columns when the same custom field name is used in both Company-managed and team-managed projects
- Gathering Interest
- relates to
-
-
- Closed
-
[API-299] Custom Fields with same names in team-managed projects not populating data when exporting
| 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. |
| Remote Link | New: This issue links to "Page (Confluence)" [ 992012 ] |
| Component/s | New: Jira Cloud for Google Sheets [ 55791 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 820113 ] |
| Link |
New:
This issue causes |
Have to agree with erika, it is annoying I had one project with Custom Fields export correctly and others not - along with other issues such as the 120 attachments then they all become non readable, not being able to clone a Project to use as a test environment like older versions allowed, for the cloning issue I've had app recommended to use, attempted to used them and they either don't work with Team Managed projects, the ones that say they do, run into errors down track and suggest that you change to Company Managed Projects to get past the issue. Whilst these issues may seem small to Atlassian added together make the application cumbersome to use. to get the desired results in a timely manner. Which overall makes it less attractive to utilizse.
| Labels | New: jsm-s16 |
| Link | New: This issue is related to JRACLOUD-77919 [ JRACLOUD-77919 ] |
| 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. |
Option 3 should be updated to specify to manually search in the field list to then add additional fields that have the same name but are different actual customfield_ids
this work-around itself is the same work-around you use in Jira Cloud for Sheets which itself suffers from the same bug. Jira Cloud for Sheets is itself not a work-around, the work-around is the same per the steps below in Daria's comment which are for Excel, but the exact same steps are what you use in Jira Cloud for Sheets to work-around this. (You can search for the different fields by the same name if you go to the Fields tab and Edit fields)
Unfortunately this isn't necessarily a minor bug though as this feature is itself how others have identified to find the customfield_id itself in the first place (and, in fact, at the time of writing this comment, that is the accepted answer even though it suffers from this bug and the i.d. you're seeing is wrong)