Feature Request: Ensure Unique Task Association (UUID Tagging)

[tegridyfarmer]

Problem

Currently, Timewarrior associates tracked intervals with Taskwarrior tasks using only the description and tags. If multiple tasks have the same description and tags, time tracked for those tasks is ambiguous and cannot be reliably attributed to the correct Taskwarrior task.

Expected Behavior

There should be a way (either by default, or as an option) for Timewarrior to always tag tracked intervals with the unique Taskwarrior UUID, ensuring that time tracked for tasks with identical descriptions/tags remains distinct and reportable per task.

Steps to Reproduce

1. Create two Taskwarrior tasks with the same description/tags.
2. Track time for each in Timewarrior.
3. Observe that intervals are not uniquely associated with each task.

Suggested Solution

• Always include the Taskwarrior UUID as a tag in intervals started via the integration hook.
• Optionally, provide a way to retroactively update intervals if a task description or tags change.
• Improve documentation to clarify the importance of UUID tagging for unique attribution.

Additional Context

This would improve reporting accuracy and prevent time from being merged or misattributed when working on similar or recurring tasks.

[lauft]

Not sure whether a rewrite of the on-modify hook script focussing on the UUID as the primary source to determine the associated interval(s) is necessary when implementing this.

By design, the hook script is only triggered by (modifications on) active tasks, so if I am not mistaken, the main use case to use the UUID would be when one has two tasks active in parallel and starts shifting one back or forth in time, especially diminishing the overlap to zero. 🤔

Providing a test scenario for an e2e test would be helpful here...

[tegridyfarmer]

Just to clarify, my situation is having different tasks with the same name, tags, and project (but not active at the same time), and it’s hard to tell them apart in Timewarrior.
If it’s truly not practical to implement UUID tagging for this, I understand and can close the issue.

[lauft]

Thanks for the clarification. In principle, adding the UUID to the list of tags is not that difficult. I am more afraid that this will break somebody else's workflow... 😅 Maybe one could make it somehow configurable...? 🤔