Refactor Time Tracking API, Revamp TimeTracking Statistics Page

[fm3]

Changes the time-tracking overview to show times spent in annotations and tasks and filter them by teams and projects. In the linked detail view, the tracked times can also be filtered by type (annotations or tasks) and project.

Backend Changes

• Removed several now-unused routes (previously used either by frontend or braintracing dbs)
• Added new route /time/overview to fill new user time tracking table, filtered by team, projectIds, onlyCountTasks
• Refactoring
  • No more JodaTime dependency, use java.time utilities instead
  • Renaming of some Methods
  • Moved more Logic to SQL
  • Integrated StatisticsController into TimeController

Steps to test:

• go to https://timetrackingapi.webknossos.xyz/
• Create several users with different rights, annotations, tasks
• Annotate some, as different users
• Time tracking overview should list all users you are allowed to see (only your orga, only yourself if you’re no team manager, only of your teams if you are team manager)
• Use Filters to select specific teams and projects, as well as switch between tasks and non-task annotations.
• Time tracking detail view should list a single user’s spent time in more detail.

TODOs:

• Backend
  • merge StatisticsController with TimeController?
  • split statistics routes?
  • make inclusion of explorative optional for /api/time routes AND statistics routes (unify those routes altogether?)
  • Move more logic to SQL
  • No more JodaTime
  • Clean up
  • No more java.util.Calendar
  • CI
  • Document changes
  • support selecting multiple teams in /time/summed/userList
  • investigate report of empty response depending on team members
  • fix snapshot tests
  • remove unused routes (api/time/groupedByInterval?, /time/allusers, /time/userlist)
  • make sure every user can see their own timetracking info
• Frontend
  • Adapt to changed api for time graph
  • Remove Best/Busiest users of the week table from webknossos.org/statistics -> maybe delete whole view
  • Add new timetracking overview table as discussed in https://scm.slack.com/archives/C5AKLAV0B/p1704359796147499
  • adapt timetracking detail view
    • to filter by projects
    • to handle exploratives (task-related entries can now be null)
  • Rethink page structure (time tracking vs statistics)

Charlies todos:

for time tracking overview

• add and fill table (sortable) in new page
• add CSV export
• link to prefilled detail view
• add filter include exploratives
• test with more than 1 user
• move initial user and daterange values for detail view to url params
• fix key in navbar
• rethink placeholder for projetcs
• time in s in csv
• fix link to detail view, possibly with router
• implement deselect
• include possibility to select only annotations (maybe talk to backend)
• fix DateRangePicker. like in time line view? plain antd? how to do presets without getting TS problems?
• fix spinner
• only visible to admins and team managers

detail view

• fix project update (somehow an old state is used after getting to view from overview)
• fix google chart, which is not showing time from sth. other than tasks

Issues:

• fixes Replace JodaTime with java.time classes #7489
• fixes Time tracking: option to include explorative annotations #5375
• fixes docker compose commands fail if local "CMakeCache.txt" exists #7707

---

• Updated changelog
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases

[dieknolle3333]

@fm3 personally I think everything works as expected with your new changes, thank you!

[normanrz]

I reviewed the backend code only. Looks good. Just one comment on time zones. Not sure we have considered these before.

I did a happy path testing. Seems to work. The UI looks slick!

[philippotto]

testing went smooth :) only one small thing:

the bullet points next to the values in the per-user-time-view look weird:

maybe use a border-less table and the • symbol in front of each label. or do it like here: https://master.webknossos.xyz/statistics

[philippotto]

front-end looks good to me 🥇