Resolve "Fields must be unique per site" #1895
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!1895
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "250-fields-must-be-unique-per-site"
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 #250
changed milestone to %"2.0a2"
added 1 commit
Compare with previous version
removed milestone
added 1220 commits
masterCompare with previous version
added 102 commits
masterCompare with previous version
added 1 commit
79ac982a- Ensure uniqueness of fields per siteCompare with previous version
marked this merge request as ready
added 2 commits
76941877- Move preference check for change password feature to instantiation3f12f2e3- Add migration for unique constraintsCompare with previous version
assigned to @hansegucker
mentioned in commit
c947120eeamentioned in merge request !2271