Features / Regression bugs / Future prospects

[JSPRH]

With our legacy Kordis system, we have a couple of smaller features (requests) and regression bugs from our internal bug tracker and from GitLab. To have them in scope for the new system, keep them in mind and make linking easier, this issue lists those requests and bugs.

Features

• List and deep link operations by operation type (Ticket)
• Operations should have a body of water, incl. statistics (Ticket)
• Station note's icon should be clearly visible if containing text (Ticket)
• Operation departments and state departments should be filled from dimensional data (i.e., drop-down) and not be free form to avoid data inconsistencies (e.g., "Hamburg" and "LV Hamburg")
• Export unit list as csv and pdf, filtered and grouped (Ticket)

Regression Bugs

• List active units only for station tooltips in map (Ticket)
• Self-host assets to avoid GDPR problems (see Material Ticket)
• On changing assignments for the special station, units listed there but not assigned get assigned (Ticket)

Leftovers from our UI/UX study that we will not implement in our first MVP release cycle:

• Documentation of what personal is appointed to what unit (Important for BG)
• New features need to be publicized more
• Weather map layers (Rain, lightning)