Aevon Timesheets Is Live: Log Time, Route Approvals, and Prep Billing Without Leaving Jira

We track our time. Not because anyone enjoys filling in a timesheet, but because it answers the one question every team that bills for its work keeps having to ask: where does the money actually go? Hours are the rawest measure of cost — track them well and you can see which clients, projects, and people are profitable and which are quietly losing money; track them badly and you're guessing at the number your whole business runs on.

So we went looking for a clean way to do it inside Jira, where the work already lives. What we found was discouraging. The established Jira time trackers are good — and expensive, often several dollars per user every month, which adds up quickly across a team. And most of them are Connect apps, which means your worklogs — who worked on what, for which client, and when — get copied out to the vendor's own servers. For data as sensitive as billable time, that's a lot to pay, and a lot of trust to hand to someone else.

We wanted the opposite: time tracking cheap enough that the bill is an afterthought, simple enough that people actually log their hours, and built so the data never leaves Atlassian's infrastructure. Nothing on the market did all three. So we built it.

Today we're launching Aevon Timesheets — time tracking, approvals, and billing prep, all inside Jira on Atlassian Forge. It runs the whole loop, log → submit → approve → bill, at roughly a tenth the cost of the incumbents and with every worklog staying exactly where it already lives. And it's live on the Atlassian Marketplace as of today.

Here's the whole thing, one screen at a time.

Log time on a calendar that behaves like one

The “easy” promise starts here. People only keep a timesheet current when logging takes seconds, so Aevon gives each person a weekly Mon–Sun grid that works the way a calendar should: click a slot to log work, drag a card to a different day, grab its edge to change the duration. Overlapping entries lay out side by side instead of hiding behind each other, a live “now” line keeps you oriented, and a timer can track in-flight work across browser tabs.

The Work Items panel on the right keeps your recent and assigned Jira issues one drag away — drop one onto the grid and Aevon pre-fills the Log Work dialog with that issue already attached.

Submit once — Aevon routes each client to the right approver

Here's the detail that makes timesheets painful for agencies and service teams: one person's week rarely belongs to one client. In the calendar above, Aria split hers across the Mars Rover Mission and the Hermes Lander Program. So who approves it?

Everyone who should. When Aria submits, Aevon groups her worklogs by account (or by project, if an account isn't set) and creates one approval request per group, each routed to that account's default approver automatically. A week that spans three accounts becomes three approvals in one click — with a Change button if she needs to override any approver before sending. The week counts as approved only when every group is.

Logged the wrong issue, or jumped the gun? Hit Recall to pull a submitted week back to draft — as long as no approver has acted on it yet.

Approvals: one inbox, not an inbox-shaped nightmare

Approvers open a single Pending approvals queue, grouped by submitter — each row showing the person, the week, the total hours, and the projects involved. Select all, approve the clean weeks in a batch, and reject the ones that need a fix. Rejecting requires a comment — so “sent back” always arrives with a reason — and returns the week to the employee as a draft.

Billing prep you can actually hand to finance

This is the step that usually lives in a spreadsheet held together by hope. Aevon's Review view pivots any date range by account into the four columns finance actually cares about: Ready to Bill, Pending, Rejected, and Not Submitted. A verdict column says the quiet part out loud — Ready to bill, Partial · chase, Has rejections — so you know exactly who to chase before you invoice.

Once hours are approved, they lock — no quiet edits after sign-off — and the full audit trail (who approved what, when, and any rejection comments) stays in Jira. When a client's column is green, Export approved CSV hands invoicing a clean, signed-off number.

Reports for everyone who asks “where did the time go?”

Beyond billing, Aevon ships a flexible Reports view. Pivot by Project, User, Issue, Account, or Category — two levels deep — and filter by projects, people, work items, billable status, or a raw JQL query when you need to get specific. Click any cell to drill into the worklogs underneath it. Two export formats come standard: a tidy pivot CSV for stakeholders, and a raw CSV for whoever owns the data warehouse.

It lives on every Jira issue — and “Account” is a real Jira field

Aevon isn't a separate place you have to remember to visit; it's a panel on every issue. Open any Jira issue and you'll see the worklogs logged against it, with quick-log shortcuts right there. Drag the issue onto your calendar and the Log Work dialog opens pre-filled.

The Account Aevon bills against is a genuine Jira custom field, not a value trapped inside the app — which means it's searchable in JQL, with autocomplete:

If you already run Argon, the two fit together neatly: Argon tells you how long an issue sat in a status; Aevon tells you how much time your team logged against it. Both answer in plain JQL.

Forge-native: your time data never leaves Atlassian

Most Jira timesheet apps are Connect-based, which means your worklogs — who worked on what, for which client, and when — get shipped off to the vendor's servers. Aevon is Forge-native. Time is stored as standard Jira worklogs, every screen runs on Atlassian's own infrastructure, and no external service or subprocessor receives your data. We've written about why we build exclusively on Forge — for timesheets, where the data is unusually sensitive, it matters even more. It's also why Aevon sails through a security review: there's no new data processor to vet. (It's covered in our CAIQ (Lite) self-assessment, if your security team likes to read ahead.)

Priced like it respects you

Aevon is free for up to 10 users, every feature included. Above that it's $0.50 per user / month up to 1,000 users, and $0.25 per user / month beyond that — about a tenth of what incumbent Jira time trackers charge at 100-user scale. Annual billing knocks off another 16%.

And there are no surprise add-ons: approvals, the billing-prep review, custom worklog attributes, and the audit trail are all in the base product, not premium tiers. You can model your own team on the live calculator on the Aevon product page. Coming from Tempo specifically? We've done the math side by side: the Tempo Timesheets alternative comparison.

Stop running timesheets through three different tools

Log the time, route the approval, prep the bill — one app, inside Jira, with the data staying exactly where it already lives. That's Aevon Timesheets, and it's live today.

Install Aevon Timesheets free on the Atlassian Marketplace — or take the full tour on the product page first.