Resolve "Allow control over self-editing of person" #2208
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!2208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "245-allow-control-over-self-editing-of-person"
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 #245
added 2 commits
4ff47207- Add preferencesCompare with previous version
added 1 commit
e1650f50- Trigger emailCompare with previous version
assigned to @nik and unassigned @debdolph
added 1 commit
Compare with previous version
added 1 commit
2fd6ad6e- Use syncable_fieldsCompare with previous version
added 1 commit
6d86bab1- Disable fields in formCompare with previous version
added 8 commits
master83fc8097- Merge branch 'master' into 245-allow-control-over-self-editing-of-personCompare with previous version
added 1 commit
97e442b6- Update lockfileCompare with previous version
added 1 commit
7d08be1c- Fix choicesCompare with previous version
added 1 commit
0e4b12c8- Disable fields correctlyCompare with previous version
added 1 commit
a990b99b- Disable fields correctlyCompare with previous version
added 3 commits
0e4b12c8- Disable fields correctly7694db61- Merge branch '245-allow-control-over-self-editing-of-person' of...3333d61a- Fix mail templateCompare with previous version
marked this merge request as ready
requested review from @hansegucker
Is the following change an option?
Also, please check if the form still works as a create form.
Missing docstring.
Missing docstring.
Missing docstring.
Also, we maybe should do this like in
DataChecksEmailsRecipientsandDataChecksEmailsRecipientGroups.changed this line in version 12 of the diff
added 18 commits
masterdf473854- Merge branch 'master' into 245-allow-control-over-self-editing-of-personCompare with previous version
added 1 commit
32a135e4- Fix creation of personsCompare with previous version
changed this line in version 14 of the diff
added 1 commit
091e559d- Apply 1 suggestion(s) to 1 file(s)Compare with previous version
I don't think so. The recipient is not always a person or a group in AlekSIS.
added 1 commit
Compare with previous version
resolved all threads
added 1 commit
a9e12912- Add missing docstringsCompare with previous version
approved this merge request
added 46 commits
masterCompare with previous version
added 1 commit
c64671b6- Merge branch 'master' into 245-allow-control-over-self-editing-of-personCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
marked this merge request as draft
added 1 commit
e71f1ea9- Use rulesCompare with previous version
added 1 commit
451fd6ae- Check rule in formCompare with previous version
added 1 commit
Compare with previous version
marked this merge request as ready
added 1 commit
6631ab3b- Check if current person is current userCompare with previous version
Please re-word to make clear that this checks the existence of a list item.
That's wrong. The code is independent of who the current user is.
This must convey that this preference is about persons editing themselves.
Use the
edit_personrule here isntead.This must be combine wit ha check on whether the person is the same as the current user.
changed this line in version 26 of the diff
changed this line in version 26 of the diff
changed this line in version 26 of the diff
changed this line in version 26 of the diff
added 1 commit
Compare with previous version
resolved all threads
resolved all threads
changed this line in version 27 of the diff
added 1 commit
Compare with previous version
Please use permission prefetching.
This needs to be comined with a check on the preference enabling/disabling editing of the person themselves.
Use parantheses to make conjunction precedence clearer.
changed this line in version 28 of the diff
changed this line in version 28 of the diff
added 1 commit
4c0c841f- Fix naming issuesCompare with previous version
resolved all threads
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
changed this line in version 33 of the diff
added 1 commit
54077d6f- Prefetch permissionsCompare with previous version
assigned to @hansegucker and unassigned @nik
requested review from @nik and removed review request for @hansegucker
approved this merge request
added 3 commits
5f896c20- Implement rules and predicates93ff633a- Add preferences92b9b545- Check permissions and send mail if enabledCompare with previous version
mentioned in commit
c7fae2a048