English
Hi everyone!

I found a workaround for this issue and was able to fill in the previously blank information in the spreadsheets exported from Jira.

Since this ticket was created back in 2020 with low priority and has not yet been addressed, I started looking for alternatives to solve the blank columns in Excel problem.

Here’s the step-by-step solution I used:

1. When downloading the file, if you notice a column that is filled in within Jira but appears blank in the Excel export, connect Excel to Jira Cloud and identify the "Customfield" number of that column.
2. Go to Global Administration for custom fields. Select any custom field, then go to "Contexts" > Create, edit or delete contexts".
3. You will see that the Jira URL contains your company’s name and ends with something like . Replace the number at the end with the custom field number you identified as being blank in Excel.customFieldId=11121
4. This will open a page showing which projects in your company are using that field (with the same name). If the project is managed by the team, a new custom field ID will be generated. In my case, I contacted the teams using those projects and advised them to use Global Administration custom fields. This prevents duplicate fields with the same name and also avoids blank columns when exporting using Microsoft Excel.

By applying this solution to all columns and fields that were returning blank data in Excel, we were able to fix the problem and guide teams across the company.
We are currently using this workaround until Atlassian provides a permanent fix.

Portuguese
Olá, pessoal!

Consegui encontrar uma medida de contorno para esse problema e, no final, consegui preencher nas planilhas extraídas do Jira as informações que antes estavam em branco.

Como este chamado foi criado em 2020, com prioridade baixa, e ainda não havia sido atendido, busquei alternativas para resolver a questão das colunas em branco no Excel.

Segue o passo a passo da solução que utilizei:

1. Ao fazer o download do arquivo e identificar que existe uma coluna preenchida no Jira, mas em branco na extração para o Excel, conecte o Excel ao Jira Cloud e identifique o número do "Customfield" referente a essa coluna.
2. Acesse a Administração Global de campos personalizados. Escolha qualquer campo personalizado, vá em "Contexts" > Create, edit or delete contexts".
3. Observe que a URL do Jira exibirá o nome da sua empresa e, ao final, algo como customFieldId=11121. Altere o número final para o número do campo personalizado que você identificou como estando em branco no Excel.
4. Isso abrirá uma página mostrando qual projeto da sua empresa está utilizando esse campo (com o mesmo nome). Caso o projeto seja administrado pela equipe, será gerado um novo número de custom field. No meu caso, entrei em contato com as equipes responsáveis por esses projetos e orientei a utilizarem os campos personalizados da Administração Global. Isso evita duplicidade de campos com o mesmo nome e também impede que as colunas fiquem em branco ao extrair dados no Microsoft Excel.

Aplicando essa solução para todas as colunas e campos que apresentavam informações em branco, conseguimos corrigir os problemas e orientar as equipes de toda a empresa.
Estamos utilizando essa medida de contorno até que a Atlassian disponibilize uma solução definitiva.

Please, help. This affects my teams work.

Hello, the method of uploading fields via CSV may work, but now we need constant up-to-date data from the database and we decided to use the Looker Studio Connector and the same problem with the fields arose here, that is, these fields are not uploaded and are not transmitted via the connector, maybe there is a solution to this problem or a deadline?

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)

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.

Hi,

Can I please ask for an update, please? This is quite a burning update for us. We can populate data from custom fields through CSV format, but for each project, the same custom fields gets a different column and you need to merge the data manual to be able to provide solid reporting. Additionally CSV format does not recognize signs from other languages hence converts them into different signs, which again speaks against the CSV export. 

Hello everyone,
I’ve tried to perform the same steps as in issue.

There are 2 Next-gen Jira Projects (TESTD2, TESTD3) in my Test Jira, each has ‘Label Test’ Custom Field (drop-down):

For each Project Issue with filled ‘Label Test’ Field is created. 

When open separate Issue, each has only one ‘Label Test’ Field. 
When search for those issues in Jira, each has two values for ‘Label Test’ Field (for each Project), for example:

‘TESTD2 US 1’ has ‘labelTESTD2_1’ value for TESTD2 Project and ‘None’ for TESTD3 Project;
‘TESTD3 US 1’ vice versa has ‘None’ value for TESTD2 Project and ‘labelTESTD3_1’ value for TESTD3 Project.
TESTD2 goes 1st in value list for ‘Label Test’ Field.

When export in Excel, only 1st value is shown for the column, in my case value for TESTD2 Project. That is why issues for TESTD3 Project have empty ‘Label Test’ Field:

Also when select Columns in Jira, this Field is mentioned just once in the list (no indication to which Project that field belongs):

Also to have Custom Field values for all Issues, User may select both these Fields in Add-In and get the following result:

Workaround: in Excel File created using 'open in Microsoft Excel' - select all Fields with the same names in Add-In and get data again. Or give different names to Custom Fields in different Projects (as mentioned in current Ticket).

Internal Ticket is created and will be taken in work basing on Team workload.