-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signed CLA is showing up as not signed on Corporate Console #2515
Comments
- Refactored GET for company, project CLAs by leveraging signing entity name - Updated response with multiple companies Signed-off-by: wanyaland <[email protected]>
- Refactored GET for company, project CLAs by leveraging signing entity name - Updated response with multiple companies Signed-off-by: wanyaland <[email protected]>
- Added company_id and signatureACL to response Signed-off-by: wanyaland <[email protected]>
- Added company_id and signatureACL to response Signed-off-by: wanyaland <[email protected]>
- Factored in internal companyID based on signing entity name to fetch corresponding events Signed-off-by: wanyaland <[email protected]>
- Factored in internal companyID based on signing entity name to fetch corresponding events Signed-off-by: wanyaland <[email protected]>
- Added query param for company ID for company project cla endpoint Signed-off-by: wanyaland <[email protected]>
- Added query param for company ID for company project cla endpoint Signed-off-by: wanyaland <[email protected]>
- Resolved events endpoint caused by incorrect filter attribute changed to event_company_id - Updated company project contributors endpoint with internal companyID as path parameter Signed-off-by: wanyaland <[email protected]>
- Resolved events endpoint caused by incorrect filter attribute changed to event_company_id - Updated company project contributors endpoint with internal companyID as path parameter Signed-off-by: wanyaland <[email protected]>
All CLA backend changes have been deployed to Dev. |
@manishv09 as discussed try it also for a new org after new org creation issue is resolved & deployed to Dev. |
Closing this ticket since it was updated on 2-Feb that signing entity name will not be shown on the UI anywhere - system will return to its old behavior. |
This issue is seen on Staging environment.
I signed a CCLA for vinodkfoundation_child1 project for "Proxima India" (it is a signing entity name in company Proxima) however the CCLA is shown as not signed on Corporate Console

When I go from Contributor Console & select "Proxima India"; it gives presents me the list of CLA managers which means CLA is signed.

CLA group information can be found below:

I called the following API from postman:
https://api-gw.staging.platform.linuxfoundation.org/cla-service/v4/company/0012M00002MnADGQA3/project/a097c000007nhFnAAI/cla
I got the following response:
{
"signed_cla_list": [],
"unsigned_project_list": [
{
"can_sign": true,
"ccla_enabled": true,
"cla_group_id": "043637e9-1a8f-4082-9a45-db1fa7d7f0dd",
"cla_group_name": "vinodkfoundation_clagroup1",
"icla_enabled": true,
"project_name": "vinodkfoundation_child1",
"project_sfid": "a097c000007nhFnAAI",
"sub_projects": []
}
]
}
The text was updated successfully, but these errors were encountered: