Skip to content
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

Hide fields in taxonomy that don't belong there post migration #3907

Closed
rsilvery opened this issue Aug 8, 2023 · 5 comments · Fixed by #3909
Closed

Hide fields in taxonomy that don't belong there post migration #3907

rsilvery opened this issue Aug 8, 2023 · 5 comments · Fixed by #3909
Assignees

Comments

@rsilvery
Copy link
Contributor

rsilvery commented Aug 8, 2023

As part of the migration of fields that Dawn, Andrew, and Jeremy are doing, we'll need to hide the following fields in the taxonomy editor:

  • Data Use:legal_basis
  • Data Use:recipients
  • Data Use:special_category
  • Data Use: legitimate_interest
  • Data Use: legitimate_interest_impact_assessment
@rsilvery
Copy link
Contributor Author

rsilvery commented Aug 8, 2023

@Kelsey-Ethyca , @pattisdr as FYI

@TheAndrewJackson
Copy link
Contributor

@pattisdr Are the above fields going to be made optional and or completely removed after the migration is done? I have the form fields removed but I can't submit the form due to failing the schema validation check from the BE.

@pattisdr
Copy link
Contributor

pattisdr commented Aug 8, 2023

Good callout @TheAndrewJackson. I am not removing anything yet to reduce risk, just adding all new fields. I will mark these as optional in fideslang (I think there was only one of these that wasn't?)

@TheAndrewJackson
Copy link
Contributor

Thanks, I'll try making a small change locally while developing to get around the schema issue.

That's correct. The field that is failing is legitimate_interest_impact_assessment

@Roger-Ethyca
Copy link
Contributor

moving to. done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants