It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Issue ID Field being added to CSV (Current Fields) and should not be. How do I remove it?

After upgrading from JIRA Service Desk 3.1.10 to 3.5.2, the Export of CSV (Current Fields) is adding the Issue ID Field to the file, even though the columns do not list it even as an available column to select.

It shows up in the second column.


1 answer

Its part of "Key" column. If you remove "Key" you will see the issue ID also is not present. 

What if I need the key in the Export?

When you get the CSV file downloaded locate the column you dont need select the letter at the top then right click and choose "Delete" It will remove the entire column and shift the data over for you without any tedious edits being needed. 

I am attempting to automate the process of generating a CSV Export from JIRA Service Desk.  Opening the export file in Excel, and manipulating the data is not a viable option.

Any other thoughts?

Whats your end goal for exporting the tickets? 

We use RSS feeds and HipChat integration to monitor tickets and updates if your looking to do something like that....

The current process is to use a saved filter that we created, Use the Export CSV (Current Fields) option, and save the file, and it is then emailed to a group.

I would like to automate this process with a Cron Job to generate the export, and send the email on a daily basis. 

We are currently looking at Addons to help us with the process, but the fields in the file have to be:


Instead I would add a dashboard with that "Filter Result" gadget. Then setup subsciptions to that board. IF they need to export it they can click the Total issue # at the bottom of the gadget to navigate to the export screen. 


We use an addon called "AIO (All-In-One Reports)" to build out reports and then setup Cron job subscriptions. 

Our reports are about the SLA in the service desk and how close tickets are to breaching the SLA, but the addon can report on just about any out of box or custom field. 

The people that would receive the emailed report dont have access to JIRA.

The report AIO sends doesnt require Jira Acess. Also, no license required for things like RSS feeds. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Desk

Tell us how you've implemented Change Management

Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...

1,747 views 10 17
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you