Let the board choose what members see and change per data field closes #669 #694
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!694
Loading…
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-669"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #669
Description of the implemented changes
The changes were:
Each data field gets a member access level: "Not visible", "Read only" or "Read and change". The board sets it on the data field's page with a radio group (one hint per option); the data fields table shows it in the column "Member access". Members see only the fields that are not hidden and change the ones set to "Read and change" on their own edit page; the server enforces both, forged values are refused. Existing data fields start at "Read only", so members see what they saw before and change nothing; a new data field starts at "Not visible".
What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
:linked(members, and the read-only roles on their own record) never read hidden fields or their values — a filter on the CustomField and CustomFieldValue reads, so every page and export follows it.update_contact_datatakescustom_field_values; a validation allows only fields set to "Read and change". The CustomFieldValue create check runs on the changeset, the update check is a filter check, because nestedmanage_relationshipupdates run as atomic updates without a loaded record. Tests send forged values for hidden and read-only fields.20261117233209_add_custom_field_member_access: the column is added with defaultvisible(existing rows), then the default becomeshidden; a migration test pins both.radio_group/1(fieldset, legend, hint per option, errors referenced per radio); empty radios get a stronger border (3.87:1 light, 4.96:1 dark).The CHANGELOG
Unreleasedsection has an upgrade note: existing data fields start at "Read only"; new ones at "Not visible".What's new: the entry for staff is in
priv/whats_new/1.7.0.exs("You now choose what members see of each data field", a task on Settings → Data fields; German texts inwhats_new.po). It stays invisible until 1.7.0 runs.docs/whats-new.mdanddocs/releasing.mdnow say that each pull request adds its entry to the next release's file and the release only curates them (at most five).