We’re using api v3. But it seems /rest/api/3/field is same as /rest/api/2/field so the solution will still work… unless you know something we need to watch out for?
Also, since we’re using /search endpoint to get a list of issues it seems we have two options
i) use regex on customfield_x
ii) include expand : versionedRespresentations and reference the JSON value inside customfield_x
Does that sound right? Do you recommend one over the other?
Using versionedRepresentations is the recomended way, since the string representation is deprecated and should not be relied on.
I would also recommend using the version 2 of the API, since version 3 is in beta. But in practice they are the same, the only difference being version 3 uses ADF, and version 2 - plain text for rich-text fields.