#205: classification inheritance + guarded, audited lowering #264
No reviewers
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#264
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue-205-classification-inheritance"
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?
Implements #205 (M26): inherit on create (max of instance default and parent), raise-on-move for the whole moved subtree, no lowering as a side effect (incl. trash-/purge-promote, pinned by test). Lowering needs the dedicated capability canLowerClassification (pond-wide Pond Admin) in the central permission model; raises and lowers audited (catalogue v1.1). Stacked on #263.