Octane 15.0.60 Interactive API Client is pulling incorrect value of fields

[Erick Vargas B]

The behavior I'm seeing in CP60 is a design of API interactive Client.

I have API key and its secret. I went to the API Interactive tool and logged to the WS with the API key.

I selected my user-defined fields and hit execute.

Yes, it gives me a report of all defects. But in the report, there is inconsistence in the value of user-defined fields, meaning the same user-defined filed is giving a list name in one defect and not giving a list name in another defect

The issue is resolved using Postman.

[tom vaingart]

Hi @Erick Vargas B ,

to be sure I got you right, the issue you are raising is the fact that the 'id' property of the two 'application_udf' fields isn't the same? or the fact that the name property doesn't being include in the swagger view compare to the postman request which does show it?

so we will better understand things, can you please also provide us:

1. the response of executing a get request from the browser to fetch the two exact defects with this UDF field.
for example, this can be done by:

{octane_url}/api/shared_spaces/{space_id}/workspaces/{workspace_id}/defects/14013?fields=application_udf

{octane_url}/api/shared_spaces/{space_id}/workspaces/{workspace_id}/defects/15010?fields=application_udf

2. the response for the two specific list nodes requests:

{octane_url}/api/shared_spaces/{space_id}/workspaces/{workspace_id}/list_nodes/brilliantyou_in?fields=id,name,activity_level,is_modifiable,is_rename_only,index,is_deletable

{octane_url}/api/shared_spaces/{space_id}/workspaces/{workspace_id}/list_nodes/{other_list_node_id}?fields=id,name,activity_level,is_modifiable,is_rename_only,index,is_deletable

you should be aware of the fact that the id property is not promised to agree to any template / format, as it's only unique identifier of the list node, so if you have two different defects which are linked into two different list nodes, they will have different ids.
if you need the friendly name of the list node, you could use the "name" property within the list node (it's not being showed in swagger, but should be returned by default when you make the same request from browser / rest client.