Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PE-D][Tester C] Functionality: cft returns a possibly inaccurate timing #231

Closed
nus-se-script opened this issue Nov 3, 2023 · 1 comment · Fixed by #260
Closed

[PE-D][Tester C] Functionality: cft returns a possibly inaccurate timing #231

nus-se-script opened this issue Nov 3, 2023 · 1 comment · Fixed by #260
Assignees
Milestone

Comments

@nus-se-script
Copy link

Unsure if this is intended behavior -- cft gives a 30 min "leeway" before the start of an event, e.g. nap starts at 1600, but cft indicates that common free time is until 1530 and not 1600. May be misleading to users.

Screenshot 2023-11-03 at 5.50.13 PM.png

This also results in cft returning a weird timing ("1500 1500") when the user / contact has 30 min of free time between events.

Screenshot 2023-11-03 at 5.56.14 PM.png

If possible, maybe can return xx29 or xx59 as the end timing.


Labels: type.FunctionalityBug severity.Medium
original: spatuly/ped#14

@owenyeo owenyeo added this to the v1.4 milestone Nov 4, 2023
@owenyeo
Copy link

owenyeo commented Nov 4, 2023

I dont think its medium

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants