Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Custom field name should be used for column header in export

Description

Custom field names aren’t appearing as expected in exports.

Steps to reproduce:

  1. create a list containing a custom field

  2. export the list to CSV

  3. open the CSV

Expected results: the custom field name heading matches the custom field name

Actual results: the column heading is custom_field_[UUID]

this is not an issue in the Ramsons release

Additional notes: As part of this fix, we will change all field names to use their human-friendly names in the export (to match the Lists app experience)

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

Activity

Show:

Kathleen MooreFebruary 24, 2025 at 1:13 PM

confirmed this is working as expected in Eureka snapshot

Emma_HaroyanFebruary 24, 2025 at 11:30 AM

Tested on Eureka Snapshot

Everything looks good.

All looks fine, after updating the custom fields

But after removing the custom fields, the exported csv file, still contains the custom fields columns. This issue will be covered here -

Noah OvercashFebruary 19, 2025 at 8:38 PM

All done! I also added automatically replacing the em dashes — with - because Excel gives encoding errors otherwise

Kathleen MooreFebruary 12, 2025 at 2:57 PM

the fix for this will update all column headers to use the translated names in the CSV (which is far more user friendly)

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Corsair

Fix versions

Release

Sunflower (R1 2025)

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 6, 2025 at 4:11 PM
Updated March 11, 2025 at 7:31 PM
Resolved February 24, 2025 at 1:13 PM
TestRail: Cases
TestRail: Runs