Explicit save button or explicit feedback on save?

[ferdinandyb]

It seems to me that anything I start writing is automatically saved, I even saw an empty task being created and then removed, but I also managed to somehow go back and loose my edit at least once.

My issue is that there is no feedback on the action. I often find myself scrolling to the bottom to see if the task was added. I think explicit save/discard buttons would be more easy to follow, but at least some sort of visual feedback whether the task was added or not would be very welcome.

Sorry if I missed something!

[doronbehar]

I too experience this as non-intuitive. There is a "Mark completed" button, and "Delete" Button, which also don't make sense when a new task is created.

[AlbeyAmakiir]

Similarly, I noticed that, when I looked at a task's details and backed out without changing anything, it updated the task with a modification marked "No changes made". This meant when I synced back to my desktop, it said that task had been modified, though nothing had changed beyond the modification history.

[skrobul]

This also bothered me, so I added a PR that implements explicit save button (#177)

@doronbehar I agree on the "Delete" button, but the "Mark completed" button makes sense if you want to do an equivalent of task log command which adds task that is already completed - I tend to use it often to log things after the fact.

@ferdinandyb agreed on lack of visual feedback being a small detail that is quite detrimental to overall user experience. The "discard" functionality is already there, just press "Delete" which again is counterintuitive in my opinion. It probably would be better if the task detail view differentiated labels depending on if the task is "new"

For new task

• "Discard" instead of 'Delete'
• "Log" instead of "Mark completed"
• "Add" instead of 'Save' (if task detail: add Save button #177 gets merged)

For existing task - no changes, so:

• Delete
• Mark completed
• Save