Phase Durations accumulating duration from all phases

[nikola-maric-aula]

Describe the bug

The phase duration is displayed incorrectly. Instead of restarting the “Voting” phase with a 14-day duration, the system includes the time remaining in the Discussion or Approval phase in its calculation. As a result, it appears as though the phase is already further along or has even expired.

original:

die Phasendauer fehlerhaft angezeigt wird. Statt in der Phase “Abstimmung” neu zu starten mit 14 Tagen, wird das Ablaufen der Phasendauer der Diskussion bzw Prüfung miteingerechnet. Dadurch wird angezeigt; dass die Phase schon weiter fortgeschritten ist oder sogar abgelaufen ist.

We definitely want to have an e2e test that mocks time passing and verifies proper phase duration calculation.

To Reproduce
Steps to reproduce the behavior:

1. ?

Info on:
Username:
Role:
Environment used:
Instance code
Browser:

[eduardoliron]

The displayed duration comes from daysRemaining() in BoxCard.tsx:22-36. For the Voting phase (phase_id = 30) the loop sums phase_duration_1 + _2 + _3 (Discussion + Approval + Voting) and adds them to box.created. So the "end of voting" is computed as:

created + discussionDays + approvalDays + votingDays

To fix this properly the frontend needs to know when the current phase began, to compute:

phaseStart + phase_duration_current

The problem is that last_update does not stamps only phase transitions. So the root cause is missing backend data, tied to a bad FE solution to work around the missing data.