Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[candidate_parameters] Consent card visible in candidate_profile #6680

Closed
CamilleBeau opened this issue Jun 8, 2020 · 6 comments · Fixed by #6807
Closed

[candidate_parameters] Consent card visible in candidate_profile #6680

CamilleBeau opened this issue Jun 8, 2020 · 6 comments · Fixed by #6807
Assignees
Labels
Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)

Comments

@CamilleBeau
Copy link
Contributor

Describe the bug
The consent card appears in the Candidate Profile page even if Use Consent setting is set to no in configuration module, contrary to what is specified by the TestPlan.

To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):

  1. From admin, set Use Consent to yes in configuration module
  2. Navigate to Candidate Profile page from non-admin account and see the consent card there as it should be.
  3. Now set Use Consent to no in the configuration module.
  4. Refresh the candidate profile page (or navigate away and back again) and see that the consent card is still there.

What did you expect to happen?
The consent card to only be visible if it is set to 'yes' in config module.

@CamilleBeau CamilleBeau added Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label) 23.0.0-testing labels Jun 8, 2020
@driusan
Copy link
Collaborator

driusan commented Jun 8, 2020

The test plan says consents need to be configured (ie. there are entries in the consent table), it doesn't say anything about any "Use Consent" configuration.

@CamilleBeau
Copy link
Contributor Author

@driusan my mistake! Closing this issue.

@driusan
Copy link
Collaborator

driusan commented Jun 8, 2020

I don't think this should be closed, we should either update the test plan to be more clear or update the code to check the config.

Personally, I don't really see the point of the useConsent option. It can be easily derived from whether any consents are configured. If there are none, then it obviously isn't being used.

@CamilleBeau CamilleBeau reopened this Jun 8, 2020
@driusan
Copy link
Collaborator

driusan commented Jun 9, 2020

Decision: add the useConsent check in a bugfix release, but not critical for the release. Look into deprecating "useConsent" as a whole later.

@ridz1208
Copy link
Collaborator

ridz1208 commented Jul 2, 2020

@zaliqarosli can you take this on ?

@driusan
Copy link
Collaborator

driusan commented Aug 6, 2020

The PR for this was merged, not sure why the issue wasn't autoclosed..

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants