Document that time-tracking, productivity tracking, pomodoros, notifications etc are out-of-scope for this plugin

[claremacrae]

Description

In discussion with @ilandikov recently, we concluded that there should be a line drawn between:

• facilities to track tasks/actions - in-scope for this plugin
• facilities to measure one's productivity on tasks/actions - out-of-scope for this plugin

Reasons included:

• It's a different domain
• It requires a very different UI...

Required Steps

Add a note somewhere in the Support and Help section explaining this, that I can point to when closing productivity and time-tracking issues....

How to Test

No response

[ilandikov]

Hi. Here is what I would suggest.

Podomoro and other time tracking techniques are focused on the time allocated to an activity, not necessarily a task. For example, one may have a task lift 10kg 20 times/buy break for dinner or an activity/event lift weights in the gym/make bread with John Doe. Note the difference in the language applied in these expressions. The former is focused on the result and has no connection with the time, while the latter is focused on the process, the time.

There is no debate on which approach is the correct one, they are complementary. Different aspects of our life are suited for different metrics.

obsidian-tasks focuses on tasks and their statuses, for example done or not done. It is not focused on activities/events/tracking time/etc.

[jroachgit]

Yeah, I can understand the difference.
The waters can get murky when you want to prioritise or filter tasks based on expected duration.
That would be the middle ground.
Then beyond that, i.e. capturing actual duration, would be where an integration with Toggl would come in handy.

[claremacrae]

I've just created a Request a Feature page - and in it I've linked to this issue...

I'm going to declare that this is good enough for now, and close this.