Closed ashav-github closed 3 years ago
For helping track down these issues, it would be helpful to enumerate the details:
Trying to track this CCLA signing request down. Can't seem to find an error.
2021-02-13T09:41:11 DEBUG cla: populate_sign_url - company - generating a docusign signer object with name: Asha clatest, email: ashav+avclatest@proximabiz.com
@David.. I happened to reproduce this issue and the root cause was getting cla-group for a project under LF Project, LLC. The child project used LFProject, LLC in the mappings records query
As updated by @wanyaland , this is deployed to DEV & Staging.
After Harold confirmed that fix is deployed to Staging, I tried it for a designed CLA Manager who has LFID & it worked fine for me on Staging, @ashav-github to try it for designed CLA Manager who doesn't have LFID.
@vinod-kadam @wanyaland I retested this on Stage and its working fine now. Test Data: New org created: Nykaa | NewLF ID: ashav.nykaa | LF Email: ashav+nykaa@proximabiz.com | GH Repo: ashav-test-stgfeb1-org1/stgfeb1-repo1
This is deployed to PROD as well.
Unable to sign CCLA. Also, CLA Manager and CLA Signatory role is not assigned in IAM to the user (doesn't have LF ID) who is elected as CLA Manager by a contributor while signing CCLA.
Pre-condition: Have a Standalone project created with Entity Type=Series LLC. Parent and Legal Parent = LF Projects, LLC
Steps:
Actual Result: It throws error message at this step 'CLA System is not able to support your request. Please Click here to open a support ticket.' If you check IAM, the user doesn't get CLA Manager and CLA Signatory. He has cla-manager-designee role.
Expected Result: CLA Manager should be able to sign CCLA without any error.