eliminating duplicate fields with csv or rest

[Georg Kellerer]

Hello all,

we migrated from jira server to jira cloud last year. as described in

https://support.atlassian.com/jira/kb/merge-two-custom-fields-into-one/

i wanted to remove duplicate fields after the migration. But the csv exporter is limitted to 10.000 issues and because of the number of our issues i would have to repeat the steps multiple times. so i wante to solve my problem with the rest api.

The call i was using looks like tis:

https://myorganisation.atlassian.net/rest/api/3/search/jql?jql=customfield_10163%20is%20not%20EMPTY%20or%20customfield_10148%20is%20not%20EMPTY%20or%20customfield_10146%20is%20not%20EMPTY%20or%20customfield_10160%20is%20not%20EMPTY%20order%20by%20created%20ASC&maxResults=100&fields={customfield_10148,customfield_10038,customfield_10146,customfield_10001,customfield_10163,customfield_10037,customfield_10036,customfield_10160}

My search produces not the results i was expecting. for e.g.:

{

    "issues":  [

                   {

                       "expand":  "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",

                       "id":  "36583",

                       "self":  "https://myorganisation.atlassian.net/rest/api/3/issue/36583",

                       "key":  "TEST-100",

                       "fields":  {

                                      "customfield_10001":  null

                                  }

                   },

   ],

    "nextPageToken":  "xxyyzz",

    "isLast":  false

}

1) In this issue none of my four search criterias is present so would expect that this issue is not in my results

2) the four criterias are not part of the fields list. In jira server it was necessary to reindex the data but in jira cloud is not. Isn't it? so why are the fields not their even though i put them in the fields list in my rest call?

i would be very happy if someone could explain me what i did wrong or misunderstood.

Thanks,

Georg

[Georg Kellerer]

Hello, 

we're talking about time date fields like begin date, ende date... select fields and plain text fields. Customfield_10001 is the default team field. Team (migrated) for example is shown on the frontend with a value where team is empty. In my rest call Team is eimpty as expected but the value of team (migrated), custumfield_10160 is not in the list

[Tomislav Tobijas]

Hey @Georg Kellerer ,

Apologies for the delay - I've got back from Team and then caught some kind of fever, so I just got back to my feet.

Anyway, have you managed to resolve this in the meantime?

[Tomislav Tobijas]

Hey @Georg Kellerer ,

Which field types are we talking about here? Text fields, select/picker fields or something else?

Also, can you see values on these work items (e.g., item with ID 36583) on the frontend UI as well or not? For example, if you're seeing the value on the Jira work item view, can you re-check if you're looking at the correct field when doing a REST API call? 👀

I do know for this one JRACLOUD-83271: Following a S2C migration, reindexing is not automatically occurring resulting in inconsistent JQL results in Issue Search > as a workaround, the section says, you would need to reach out to the support team to do the fix.

Cheers,
Tobi