38 lines
2.2 KiB
Markdown
38 lines
2.2 KiB
Markdown
## NOT ALLOWED TO TOUCH THIS; ONLY HUMANS CAN EDIT THIS FILE
|
|
|
|
- Bug in the planning when it repeats yearly: It is taking the exact same dates, but the way you usually take time off is week based, so 5th-11th of october 2026 is a monday through sunday, but for 2027 it looks like I'll take time off from tuesday to the following week's monday, which is not what I will do. Instead for 2027 I will probably take 4th to 10th instead.
|
|
-> DONE
|
|
|
|
|
|
Following three have a plan (free-days-and-auto-planning-plan.md):
|
|
- Please just verify that if I say that I take a full week time-off, including saturday and sunday, that I will NOT actually take any vacation or PL during those days. Or rather: This should be a setting: Take PL during red days yes/no. And it should default to NO. It is impossible to take vacation during red days (and saturdays), but you can actually take PL to get more money, but you will of course loose days.
|
|
|
|
- If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
|
|
|
|
- On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days.
|
|
|
|
-> In progress, super long time.....
|
|
|
|
|
|
- Problem with the yearly timelines in general tab
|
|
-> alignment-plan.md -> DONE
|
|
|
|
## Below here is taken from another markdown file, so should probaby be filtered and removed
|
|
## High prio
|
|
|
|
- If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
|
|
-> have a plan I think
|
|
|
|
- On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days.
|
|
-> have a plan I think
|
|
|
|
- Use fabel to go over the frontend to analyse what can be extracted into proper components and reused that today might be implemented multiple times: "Component Extraction"
|
|
|
|
## medium prio
|
|
- Update all deprecated things in the backend code.
|
|
-> fix-deprecations-backend-plan.md -> DONE
|
|
|
|
## lowest prio
|
|
|
|
- check if the security audit findings have been done
|
|
-> yet to have a plan |