As a user of the deck app I would like to be able to see how much time I have spend on a task represented by a card. After completing a project I want to see how much time I spent in total and on each sub task. I want to see whether I maintained an allotted time budget and to be able to report it.
I think this could be implemented with a button on each card. The button could follow the common "record" symbol and when clicked would start a counter for this card. On start the button changes to a "stop" symbol (square). Alternatively the buttons can simply be called "Start Tracking Time" and "Stop Tracking Time".
Each card has a rectangular area displaying a time in hh:mm:ss format. It is greyed out when no time has been record. The time starts counting when a user presses the record button and stops when the user stops counting. It continues running when a user starts the button again.
There is a cumulative display for each project that displays the sum of all cards.
I am thinking about implementing this. Has anyone else done anything in this regards or would be willing to join forces?
We have a customer interested in a time tracking app in Nextcloud, but not Deck specific
https://github.com/nextcloud/tasks/issues/75 is the related issue from the tasks app. Since this is quite a huge feature with lots of open questions both technically as well as from a user interaction perspective, I'd definitely say that the general implementation idea should be somehow sorted out before actually writing some code.
Might be interesting to integrate with the new https://github.com/te-online/timemanager app by @te-online. It would probably be nice if there would be a way to easily create time tracking entries that are somehow associated to a specific task and on the deck app we could offer some API so that the time tracking app would be able to list the task related times right within the cards.
Most helpful comment
https://github.com/nextcloud/tasks/issues/75 is the related issue from the tasks app. Since this is quite a huge feature with lots of open questions both technically as well as from a user interaction perspective, I'd definitely say that the general implementation idea should be somehow sorted out before actually writing some code.