Forums

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

Custom field appears twice in export, one with information, the other with nothing

Dean Stearn
Contributor
September 17, 2021

Hi...When I migrated to JSM, I created a custom field to capture the old ticket reference from our old ticketing system. This is a single line text field called SLRef.

When I now export data, I face two scenarios based on the export method I use:

1 - My filtered view has the SLRef visible, but shows no data on screen (do not know why). However, if I then export the data using this filtered view using the method Export / Export Excel (CSV) (current fields), the field appears twice in the export. One has no data, the other has the data. Both fields have the heading   Custom field (SLRef)

2 - The other method I use (which is my preferred choice) is because it does not have a limitation in the number of records I can export, whereas the first method only exports 1000 records. However, the problem I have with this method is that the SLRef field exports but is the one without the data.

 

I have attached a couple of screenshots that demonstrate what I see.

Furthermore, there is another custom field called 'Custom field (Ireland Ticket Reference) which also appears twice in one of the screenshots. Again, I only have one custom field of this name set-up but there is a slight difference in that one uses proper case (which is the one set-up and the other does not). Where are these fields being pulled from.?

I have checked my custom fields but cannot see what is causing this behaviour.

Can anybody shed any light on what is causing this odd behaviour.

Thanks

Dean

SLRef Custom Field Setup.PNGSLRef Custom Field in export current fields extract.PNG

 

 

 

1 answer

1 accepted

0 votes
Answer accepted
Ivan Lima
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2021

Hi @Dean Stearn, the scenario you described looks similar to this one, JRACLOUD-76648 and MIG-779, reported in the Atlassian public issue tracker. Have you checked if there is a team-managed project using fields with the same name?

Dean Stearn
Contributor
September 20, 2021

Hi @Ivan Lima

Thank you for this, this is exactly the issue I am facing. We have numerous projects on the go and these fields will have been set-up on those as well, they are most probably team-managed projects.

I'll go through each of the projects and tidy up where necessary.

 

Thank you

Dean

Like Ivan Lima likes this
Dean Stearn
Contributor
September 20, 2021

Hi @Ivan Lima , just an update on this.

I found a couple of team-managed projects that contained the rogue fields and I have removed them. My extracts are now coming out as expected.

Thank you for your help.

Kind regards

Dean

Like Ivan Lima likes this
Ivan Lima
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 20, 2021

Nice one. I'm glad it worked 👍🏻

Like Dean Stearn likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events