Deadlines mandatory #190
Labels
No Label
backlog
bug
duplicate
enhancement
feature
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
in discussion
invalid
priority
1
priority
2
priority
3
priority
4
priority
5
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: IT-Naturschutz/konova#190
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Status quo
Deadlines are optional and not mandatory. They are not being verified during quality checks.
Enhancement
There are certain deadlines, mainly for compensation-like objects (Compensation, EcoAccount, Ema), which should be mandatory or at least be present on quality checks. Quality checks are being performed e.g. during recording to ensure all 'soft-mandatory' data has been entered.
Mandatory deadline types
The mandatory deadline types is
FINISHED
. Every entry has a deadline which describes when the compensation has to be done.Other deadline types can not be mandatory (or soft-mandatory) due to individual reasons (e.g.
MAINTAIN
describes a deadline up to which the compensation needs to be maintained --> does not always exist).Display need for soft-mandatory deadlines
Keep it small and simple: Similar to the unequal-state-warnings on before_state and after_state, we can simply add a similar message, which states that at least the following deadlines must be entered: x, y, z
This way even unexperienced users know what to do.
Merged in #194