requester somok.guptaroy@shell.com

Type of issue: Feature Request
Somok Gupta Roy sent a feedback.
Description: I would like to request you to consider a feature request for the GET Task Brief (GET /tasks/{id}/brief API. The response for this API returns the fields that are part of the Task brief, carried over from the Work Request. In the field array, we get the information as name and value combination. Other similar APIs like the GET Task field (GET tasks/{taskid}/fields or GET Task Asset field (GET /tasks/{taskid}/assets/{asset_id}/fields return the field ID along with the name and value combination.
Can the API response for Task Brief also contain the field ID? Right now we are dependent on the field name and if the name gets updated, it has an impact on the automation which is trying to read the value of a field. If we get the ID in the API response, then any change to the name will not impact the automation and it will continue to work normally.
We have the same setup implemented for template id, task id, step id and sub-step id as well. It is only for the Task Brief that we are dependent on the field name since we dont get the ID back in the response. Please let me know if you need any other information or if you feel this can be added to your feature request.
User email: somok.guptaroy@shell.com
User id: somok.guptaroy@shell.com
Account: Shell UAT
Account id: 8ef0bf48-f16c-72ce-6356-41f25b5aaaf2