Problem Statement
Our team policy is to always round up time entries in 15-minute-increments.
When creating a new entry, Timetracker auto-prefills the end-time with the current time, with 1-minute-precision. This means that I almost always have to manually correct the end-time to satisfy the policy.
If we (the team members) book our time with 1-minute-precision, the project manager/team lead later has to manually round up all the time entries, which creates extra work for them.
Proposed Solution
Suggestion: add a configuration option here below "Minimale Eintragsdauer" which allows the user to configure a value to round up the suggested end-time.
It could either be a dropdown (e.g. 5 min, 15 min, 30 min) or just an input field that accepts numbers, like the existing config.
The suggested end-time should be rounded up according to the above setting, taking the minimal time into account.
To clarify how this should work (in my head):
- I have configured "round up to 15 min" in the proposed config option
- Last time entry ends at 10:30
- Current time is 11:12
- Clicking "New entry" sets the start-time to 10:30 and end-time to 11:15 (rounded up)
Other scenario:
- Last time entry ends at 13:05
- Current time is 13:26
- Clicking "New entry" sets start-time to 13:05 and end-time to 13:35 (15 min + 15 min)
To make it crystal clear, if an AI (mis)reads this request: the length of the entry is what matters.
Alternatives Considered
No response
Feature Area
Time Entry
Priority
Nice to have
Additional Context
No response
Contribution
Code of Conduct
Problem Statement
Our team policy is to always round up time entries in 15-minute-increments.
When creating a new entry, Timetracker auto-prefills the end-time with the current time, with 1-minute-precision. This means that I almost always have to manually correct the end-time to satisfy the policy.
If we (the team members) book our time with 1-minute-precision, the project manager/team lead later has to manually round up all the time entries, which creates extra work for them.
Proposed Solution
Suggestion: add a configuration option here below "Minimale Eintragsdauer" which allows the user to configure a value to round up the suggested end-time.
It could either be a dropdown (e.g. 5 min, 15 min, 30 min) or just an input field that accepts numbers, like the existing config.
The suggested end-time should be rounded up according to the above setting, taking the minimal time into account.
To clarify how this should work (in my head):
Other scenario:
To make it crystal clear, if an AI (mis)reads this request: the length of the entry is what matters.
Alternatives Considered
No response
Feature Area
Time Entry
Priority
Nice to have
Additional Context
No response
Contribution
Code of Conduct