The Jira report data is all in just one column in Excel

Question

Hey Team,

My organization and I were experiencing issues exporting a filter from Jira to Excel. It happens that when we export to Excel, after dividing the text into columns to organize it, after a certain line the information from all the columns remains in just one column, disrupting the entire organization.

Has anyone seen something like this and knew how to solve it?
Thanks for the help!

Ana Luiza Chagas · Answer

Hi @Katrina Lieber

After some testing, I realized that this is due to the number of fields selected for export. After selecting a few fewer fields and exporting, the report works perfectly.
But I still hope to be able to export all the necessary data without all the data being in the same column. I checked and there are no characters different from the other columns that remain normal.

Thanks for the help!

Katrina Lieber · Answer

Hi @Ana Luiza Chagas ,

Thanks for following! So bummed this problem is still occurring for you. Have to tried looking closely at the custom fields in the 420th item you are trying to export? Perhaps there is an invalid/unsupported character in one of your custom fields, such as a comma or another character, that is causing this error.

You could try exporting that 420th item alone and see if the same error occurs with just the one issue's data. This would help you narrow down if the problem is caused by some data in one of the fields for this particular issue.

Wishing you the best of luck!

Ana Luiza Chagas · Answer

Hi @Katrina Lieber

Thank you very much for the response to the video, it was super educational, I took the opportunity to follow your channel!
My problem unfortunately continues to occur, I've tried to organize it in other ways but the information in some lines is simply concentrated in just one column. This happens around item 420 and we have over 600 items in the report.
I don't know if it could be due to the amount of data in the report, but I followed the same steps as you, it works for other reports, but for this specific one I still get the error.
]

Thanks again for the response!