Open dilyanpalauzov opened 5 years ago
That's a correct statement. I don't consider this an issue though. Why would I want to create a task without STATUS
?
Scheduling a VTODO means sending emails to attendees. This emails contain in the best case, apart from the iCalendar object, also rendered information in text/plain and html format. When the STATUS is insignificant, it is not set and has not to be rendered to plain text/html.
When I view the created tasks in Gnome Evolution it shows in the Preview of a task the significant (set) data. If there is no status, it does not render the status in the Preview.
As for me the Status is insignificant, I do not want to see it rendered in the Preview.
I see. So "no status" means something like "just not completed yet"? In general I don't mind allowing "no status" as well. This may require a number of changes in the UI and, more importantly, we have to provide a smooth transition in case sync apps can't handle a null
status.
Our sync app can handle an absent status in OpenTasks, but at present it defaults to "NEEDS_ACTION" if a modified VTODO on the server has no status. It won't crash though.
Another related issue: at present there are a couple of places which automatically set the task status, e.g. when you tick an item on a check list or when you resume a completed task. We'll have to review each of those and decide how to handle these.
Status: NEEDS-ACTION means not completed yet. No status means that the status is irrelevant, like no location, no attendees, no priority.
In other words, when something is competed I delete it and when it is present in my workflow it means "not ready".
Got it. I'll think of a way to make this work.
+1 for "No STATUS". I cannot edit task in OpenTasks because it get "Need action" automatically. Despite it need no any action.
Seems 2.5 years is too short for fixing this bug.
RFC5455 permits for an iCalendar VTODO object to have no STATUS: , but OpenTasks cannot create objects without STATUS.