# Proposal: Time Logging, Budgeting & Accounts for Taiga

**URL:** <https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950>\
**Category:** Contribution\
**Created:** [September 12, 2026, 11:49pm UTC](https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950 "2026-09-12T23:49:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christofer\_Chavez](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/christofer_chavez/32/6153_2.png) [@Christofer\_Chavez](https://community.taiga.io/u/Christofer_Chavez)\
**Post date:** [September 12, 2026, 11:49pm UTC](https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950/1 "2026-09-12T23:49:07Z")

</div>

Hi @TaigaTeam and community,

I am Christofer, a developer at OpenCraft, and we’re currently evaluating Taiga as a[replacement for Jira](https://forum.opencraft.com/t/replacing-jira-at-opencraft/1741/93) across our organization. Taiga covers most of what we need out of the box, but we’re missing three main things: Time Logging, Budgeting, and Accounts (a lightweight entity for grouping/billing work).

**Before anything else: we are not proposing a play/pause timer**. We read the existing discussion on _Why is there no Time Tracking?_, and our proposal is designed to be consistent with that position — not to reopen it. What we want to build is a structured, native version of the workaround the team already recommends in that thread: manual time logging plus reporting, extended with budgeting and account-level tracking, mainly to support internal billing and budget management.

**Our intention is to build this upstream-first.** So it becomes part of Taiga core and benefits the wider community. We believe it’s a good fit for core because:

- It doesn’t touch the contested “timer” feature; it’s built on the same manual-entry approach Taiga already suggests as a workaround.

- It addresses a real, recurring need the community has raised (accurate time tracking for billing), without adding scope Taiga has chosen not to support.

We’ve put together the full set of user stories — what each feature does and the acceptance criteria for each — here:[Proposal Document](https://docs.google.com/document/d/1osmFqFBiO_O5rRAufbYi2zb87Rk_HqDWq8st5mvFucY/edit?usp=sharing)

A couple of questions we’d love your input on before we start development:

- Would this be something the Taiga Team could accept as a contribution to Taiga Core?

- If not as core, would the Taiga Team be open to officially adopting and maintaining this as a plugin, rather than it staying as a plugin we maintain entirely on our own?

We’re happy to follow whatever process works best on your end: discussing scope further, preparing wireframes, or anything else needed to move this forward. Looking forward to hearing your thoughts.

Thanks!

---

<div class="post-metadata">

**Author:** ![uncoy](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/uncoy/32/5319_2.png) [@uncoy](https://community.taiga.io/u/uncoy)\
**Post date:** [September 19, 2026, 11:11am UTC](https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950/2 "2026-09-19T11:11:49Z")

</div>

We were faced with this issue about five years ago, we’d been using sophisticated software like Toggle to log time. Then Toggle decided to become really expensive and add project management. So we switched to Clockify, whose manifesto was inexpensive time tracking. Then Clockify became enterprisse software with some kind of project management of its own.

What we finally settled on is Kimai. It’s a little bit more time to set up in the first place but Kimai looks good and doesn’t change. So we use whatever project management tools we need. Time tracking is independent of the tools so no matter what happens to project management our time tracking and billing remains solid.

Other tool and workflows have changed in this time, but we’ve barely had to touch Kimai. As a bonus, since Kimai is open source and mostly CSS and javascript one can customise any screens one wants easily for faster logging.

I’d heartily suggest divorcing project management and time tracking.

---

<div class="post-metadata">

**Author:** ![Christofer\_Chavez](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/christofer_chavez/32/6153_2.png) [@Christofer\_Chavez](https://community.taiga.io/u/Christofer_Chavez)\
**Post date:** [September 22, 2026, 5:39pm UTC](https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950/3 "2026-09-22T17:39:34Z")

</div>

Thanks @uncoy for sharing your experience with Kimai. We really value the input and want to keep collaborating with the community as we figure this out

That said, this isn’t a preference we’re weighing for us; it’s a hard requirement: we track and enforce specific budgets at the individual ticket and epic level as part of how we run projects, not just for billing. Our use case goes beyond logging time and feeding a billing pipeline; we also actively manage budgets, and we track how much time has been spent and how much remains, in real time, as work progresses.

Staying within budget is something we watch closely, and that’s harder to do well when Epics/User Stories/Tasks live on one platform and the budget/time data lives on another; you lose the ability to see “how are we doing on this Epic’s budget” at the exact moment you’re looking at the Epic itself, and risk the two systems drifting apart. Having it all on the same platform is what makes that manageable for us.

---

<div class="post-metadata">

**Author:** ![uncoy](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/uncoy/32/5319_2.png) [@uncoy](https://community.taiga.io/u/uncoy)\
**Post date:** [September 22, 2026, 10:56pm UTC](https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950/4 "2026-09-22T22:56:25Z")

</div>

@Christofer_Chavez Any attractive and fast project management tool with viable in app tracking will cost at least thousands per year. Basecamp does time tracking but as a $540 flat rate add-on (if your organisation is one of the lucky ones to be grandfathered from the flat rate days, 37signals gave that up a few yearrs ago). Everywhere else where the project management is viable and the time tracking iss good enough to use, it’s stiff per user monthly fees. Count about $15/user per month minimum.

As you know some of these enterprise style solutions run to $50/user per month. Taiga is nice light and fast and affordable. Focused on project management and not on time tracking.

~~Sorry for the tone, but it’s tiring to hear people project enterprise style features on great open source projects. It’s a miracle that something like Taiga exists. And now since it doesn’t launch rockets and make free espresso for the whole team, it’s not good enough.~~

Okay you guys are planning to build it yourself and offer it to the community. Fair enough. Good luck with the time tracking project. It will be a great addition when/if it gets done.

---

<div class="post-metadata">

**Author:** ![ali](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@ali](https://community.taiga.io/u/ali)\
**Post date:** [September 29, 2026, 4:20am UTC](https://community.taiga.io/t/proposal-time-logging-budgeting-accounts-for-taiga/8950/5 "2026-09-29T04:20:23Z")

</div>

Hi, a colleague of @Christofer_Chavez’s here.

> [@uncoy](#):
>
> Okay you guys are planning to build it yourself and offer it to the community.

Yep, that’s the idea. The main driver for us is that this solves a real need internally: we need to be able to manage time and budgets alongside our Epics/Stories/Tasks. But we also think the same functionality could be useful to other teams, which is why we’re happy to put in the work to build it and contribute it back to the community.
