Extra field needed in GET call to `/clearingrequests` rest api

[amritkv]

Description

In response to the rest api /clearingrequests extra filed needed as mentioned below :

1. Project name
2. Open releases
3. Clearing progress
4. Created on
5. Agreed clearing date (it's not always coming in response for all CRs)
6. Clearing type
7. Requesting User (Currently, the email is there in response, but the table needs name as well)
8. Clearing Team (Name & Email)
9. Request closed on

[afsahsyeda]

@amritkv Most of these fields are already available as part of other endpoints and a few like clearingType and createdOn are available as part of the CR document.

[amritkv]

@afsahsyeda We need these extra fields just to reduce the redundant calls to backend. What best we can do is, out of these total fields we can divide them into different parts of the response data.

Example : For individual CR's

• created on, clearing type, request closed on be in base response part
• project name, requesting user's name, clearing team's user name can be in embedded part