You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 13, 2024. It is now read-only.
When using a magic link to report your work, the remaining effort field will always be 00:00 instead of the previous value. This causes remaining effort estimations to be completely destroyed as soon as someone reports time on a task using a magic link.
To Reproduce
Have a task with remaining effort that is not 00:00 e.g. 08:00
Create a magic link for that task
Use magic link to report work
Remaining effort is now 00:00 and your estimation is destroyed 🙃
Expected behavior
The field remaining effort is pre-filled with the previous value. This is what happens if you report your work manually without a magic link.
Desktop:
OS: Ubuntu 22.04.4 LTS
Browser: Google Chrome
Version: 122.0.6261.94 (Official Build) (64-bit)
Additional context
Please consider the urgency of the matter in your prioritization as currently remaining effort estimations are being destroyed daily and there is no use in them if they are incorrect.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using a magic link to report your work, the remaining effort field will always be
00:00
instead of the previous value. This causes remaining effort estimations to be completely destroyed as soon as someone reports time on a task using a magic link.To Reproduce
00:00
e.g.08:00
00:00
and your estimation is destroyed 🙃Expected behavior
The field remaining effort is pre-filled with the previous value. This is what happens if you report your work manually without a magic link.
Desktop:
Additional context
Please consider the urgency of the matter in your prioritization as currently remaining effort estimations are being destroyed daily and there is no use in them if they are incorrect.
The text was updated successfully, but these errors were encountered: