How to mark a task as complete?

John

I have been evaluating WorkingHours for a few days and general like it. However I do not see a way to mark a task as complete. If I hide a task, it is no longer shows up in the analytics, etc. which is not a very desirable behaviour for me. If I delete a task it seems to delete everything concerning it, which again is not a desirable behaviour. On the task list I can sort to see things in a satisfactory order, but I can imagine over time that this list is going to get unbearably long. Am I missing something or are tasks meant to be so generic that you would never think to need to remove one?

timo

Can you explain what effects exactly you would want to see by "marking a task finished"? Where would you want to still have it show up and where not? I indented the "hiding" feature for this.

D1g1t4LNrg

timo Hello Timo, well, I for one would like the ability to add a deliverable that the tasks would be assigned against. So a Deliverable = Parent item that has many Sub Tasks = Children Items. The percentage of the tasks roll up to the parent deliverable as to what percentage it is complete. Also, what roadblocks/impacts are "stopping/hold" or "slowing down/restart a task" a particular "child" task. A good example of that would be an engineering change is being implemented and you have to wait until it is complete to work on the original task. One other item would be to include what the steps forward would be available for the "impacts". I was also wondering what language you wrote this in?

John

For me, ideally it would not show up in the start work list (I actually use the Pomodoro, but the idea is the same), but would show up in the time tracking list and in the analytics. The hide task feature does basically the same thing and I would be happy to just use that, but it apparently hides the task on the analytics and on the time tracking list. Because it hides the task from the analytic view I lose some insight as to where my time is being used.

timo

So it only should hide the task from the start work button list? I don't know if this would be worth implementing. As you said yourself, you can sort the task (to the bottom) to make it less visible. I cannot implement all different kinds of "hiding". Some users perhaps would want to hide the task from the analytics, but not from the time tracking list or vice versa. I think I need to keep it simple with the hiding feature - unless a large amount of users convince me otherwise 🙂

John

I agree that infinite customization is not necessarily a good thing. May I ask what the thought process was on hiding tasks that have work units on the analytics? I am curious as to why one would want to hide work that they did, perhaps that would reveal a more efficient workflow for myself.

timo

I think most users are using a WorkingHours "task" to represent a real-world "project" or "client". I could imagine that they want to see only work for a specific task in the Analytics.
And I mean with "hiding tasks in Analytics" you mean (un)selecting (by clicking) the tasks on the bottom of the page? That feature felt natural to implement to me, it doesn't have any side-effect on other parts of the app, doesn't require additional translations and doesn't clutter the UI, that's why I added it.

mrtwinkler

I am heavily interested in the feature OP described. I thought hiding a task did the trick until I found out that this also hides the task from the analytics.

So my proposals would be either:

A) Hiding a task only hides it from the quick select menu, not from analytics. If you want to show analytics only for a specific task, place a filter there.

B) Implement a feature to set tasks done. This will hide them from the task list and the quick select menu, but not from analytics.

To give an example why this is very important to me: We track worktime based on projects/issues. The quick select menu from just half a month of tracking already has 20 items. Things will get messy pretty soon.

timo

I have set up a separate discussion with a poll here, would be great if you could participate - thanks!

timo

D1g1t4LNrg I am afraid that at this stage of the app, it is rather unlikely to implement such a drastic change in how tasks work. There are many other feature requests that I can implement faster and with less risk.

D1g1t4LNrg I was also wondering what language you wrote this in?