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

GTasks: scheduling time always at midnight #199

Closed
Marukesu opened this issue Feb 27, 2021 · 2 comments · Fixed by #204
Closed

GTasks: scheduling time always at midnight #199

Marukesu opened this issue Feb 27, 2021 · 2 comments · Fixed by #204

Comments

@Marukesu
Copy link
Contributor

What Happened

Trying to create or change a scheduled task from GTasks results with the time set to 00:00 from the scheduled day. On the
GTasks app it don't have a time setted.

Expected Behavior

That the task save the time defined.

Steps to Reproduce

  1. Create a new task on a GTasks task list.
  2. Set a scheduling day and time. (Tomorrow, 10:00, for example)
  3. see the task save only the day. (Tomorrow, 00:00)

Platform Information

ElementaryOS 6.0 Early Access. Tested with flatpak and non-sandboxed versions

@marbetschar
Copy link
Member

Seems like GTasks no longer returns the time - or at least EDS is no longer able to read it correclty (If I recall correctly, this used to work at some point).

Can you confirm, you can't see a time field for the scheduled time in Evolution for the tasks in question (see below for how it looks like when coming from Nextcloud)?

GTasks

As a reference, this is how it looks like for a task returned from a Nextcloud backend:

Nextcloud

@Marukesu
Copy link
Contributor Author

Marukesu commented Mar 1, 2021

Yeah, i can confirm that evolution don't have the time entry too.
isn't best to use libgdata to manage task from GTask? since it return the date in unix epoch, i assume it can set the time too.

Edit: ok, i'm dumb, GTasks API discards time.

so we probably don't want to show the time or set one when editng a gtask.

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.

2 participants