The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

while exporting Jira chart project name is not correct and added – instead of space

rajneekant.pathak
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 13, 2025

Project name is not correct after csv export. In case there is space between two words its added –  for that. In our case here is the correct project name -> HWSS – Connections

but in csv export it is HWSS – Connections

similarly  for HWSS – Financial Manager and HWSS – Premium Payments Consenting – TBA, CBA, SmartBen below one is coming in csv export.

HWSS – Financial Manager
HWSS – Premium Payments Consenting – TBA, CBA, SmartBen

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Arek_ Fedorowicz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 14, 2025

Hello @rajneekant.pathak

Thank you for raising the question!

Is there any chance you could specify how you're exporting the chart/dashboard?

It appears that the dashes (-) are presented as â€”, not the whitespaces, and it might be due to the encoding of the CSV file. It'd be great if you could follow the steps outlined in this third-party article to determine the encoding of the exported CSV file, and also if you could verify if the same is shown when opening the same file in any other tool, even notepad.

I tried reproducing the behaviour by exporting the chart directly and also exporting the dashboard after querying the project name from the jira_project_live table, but the dashes are presented as expected. Thus, having any additional context would help us understand whether we're dealing with a bug in Analytics or if it's something on your end that's causing the current behaviour.

Best,

Arek

TAGS
AUG Leaders

Atlassian Community Events