When I export issues to a CSV, "custom field" information

Question

When I export issues to a CSV is there a way to not have the results show "Custom Field (field name) in all custom fields.

Example:

Custom field (Benefits)
Custom field (Block Details)
Custom field (Capex Value)
Custom field (Case)

How can we remove it?

Any configuration, plugin?

Andy Heinzer · Answer

Hi everyone,

Took another look at this problem and I think my previous answer is now incorrect or was specifically for a version of Jira Server.  Having taken a new look at this in Jira Cloud I can see that all CSV exports of issue data appear to create these columns by these names of "Custom field (xyz)".

This is something we are tracking over in JRACLOUD-62216.  That ticket has details of a potential work-around where instead of using the CSV export option, you could use the export HTML option instead.  It appears this method has slightly different titles for those fields.  From there it mentions you can change the extention of that file from .html to .xls and use Excel to be able to open that file.   However it's not clear to me if other applications such as Google Sheets, or Apple's Numbers application would be able to open this specific type of file here, but this might help some others that run across this.

I hope this helps.

Andy

suresh kumar maddali · Answer

I have same issue, when i export selected fields, I am getting custom filed( filed name) is coming, Is it default behavior in JIRA cloud when we export selected fields data into CSV?

Andy Heinzer · Answer

Ah, well in that case, it could be that your new system has setup those custom fields as global custom fields.   Global custom fields appear in all projects.  However if your custom fields are not global, then they have specific contexts in which they are used by specific projects.  This is how your old system could have that field, but not have that field appear in projects where it is not supposed to be used in.

It sounds like the old system has those fields names, but they are not global custom fields, and they only exist in specific contexts for some projects, it could explain why this behavior is happening.

Take a closer look at Configuring a custom field.  It explains in more detail about setting up a custom field.

If you plan to try to change this in the new system, please see the KB called Change Context for an Existing Custom Field Without Losing Old Data.  It's very important that you follow those steps if you're going to be changing the context of the custom field.  Doing so can cause data loss in that field.