Tough question. There is no consensus about time tracking in agile methodologies. Some people think agile methodologies are not meant to include time tracking, while some really need time tracking for a variety of different reasons. Either way, Taiga is built to accommodate multiple use cases.
But, of course, agile methodologies are meant to be malleable, so even if we decided to not implement time tracking as a feature in Taiga, teams are implementing it by using workarounds (like adding hours in the task or user story title, etc.)
To accommodate these practices we came out with something that could fit in any team workflow and solve many different problems: custom fields.
Solution 1: Set Up Custom fields
You can create custom fields in issues, tasks and user stories to track everything and make beautiful reports with your favourite spreadsheet and the CSV reports functionality.
Toggl is cloud-only, proprietary SaaS so it’s not really a proper answer
I’m shocked to see how nothing except crappy Bitrix24 is capable of tracking time by pressing a “Track” and “Pause/Stop” button
It’s logical, it’s convenient, it’s all in one app, if rest of bitrix wasn’t crap that’s probably what everyone would use at this point
Most developers are freelancers/hourly-paid contractors/hybrid employees, and you need to know the time spent to actually invoice someone, so how is that not a necessity is wild to me
I use [toggl](https://toggl.com/). I’ve worked with many time trackers and toggl is excellent. The desktop app is excellent.
I have a macro setup that takes the title of the task/user story/issue.
It extracts the title and project details then it creates a new time entry.
If you want to use taiga by itself, use the statuses correctly.
Each time a status is changed it is timestamped. You can see those timestamps in the activity tab. Then export that data.
If this request isn’t met after four years, should we try to implement it ourselves? Toggl is an interesting solution, but we’d prefer a single workflow rather than switching between tools and… it isn’t open source. Do you accept pull requests for new features, or should we implement this as an independent fork?
