Aevon Timesheets
Time tracking, approvals, and billing prep — all inside Jira.
Aevon Timesheets is a Forge-native app for logging time, routing approvals per account, and producing billing-ready hours. Worklogs, approvals, and audit trail never leave Atlassian. Roughly 1/10 the cost of incumbent Jira time trackers.
Install Aevon TimesheetsSecurity & compliance
Aevon Timesheets is covered in our CAIQ (Lite) self-assessment.
The full time-to-bill loop in one app
From the calendar to billing-ready hours — without data leaving Jira.
Calendar
Log time without leaving the week.
A familiar Mon–Sun grid. Click any slot to log time, drag cards between days, resize to adjust duration. Worklogs that overlap lay out side-by-side automatically.
A timer widget tracks the in-flight task across tabs. A live "now" line keeps you oriented on today's column.
Submit & Approve
Submit a week. It routes to the right people automatically.
When you submit, Aevon splits the week into approval groups by account (or project, if no account is set). Each group routes to its own approver — three accounts, three approvers, one click.
Approvers see a consolidated inbox grouped by submitter, with batch approve and required-comment rejection. The whole week is approved only when every group is approved.
Billing prep
Finance gets a view they'll actually use.
Pick a month. See every account's hours broken out by approval state — Ready to Bill, Pending, Rejected, Not Submitted. A verdict column tells you at a glance: "Ready to bill", "Partial · chase", "Has rejections".
Export approved hours to CSV for invoicing. Approved worklogs are locked — no after-the-fact edits, no audit surprises.
Reports
Pivot the way you think.
Group rows by Project, User, Issue, Account, or Category. Filter by projects, users, work items, billable status, or full JQL. Click any cell to drill into the underlying worklogs.
Two export formats: a pivot CSV for stakeholders and a raw CSV for the data team.
Built for everyone in the loop
One app. Four very different days.
Employees
Drop time on a weekly grid. Submit on Friday. Recall if you spot a mistake. That's it.
Approvers
One inbox per week, grouped by submitter. Batch-approve or reject with a comment. No spreadsheet attachments.
Admins
Set worklog rules, approvers per account, custom attributes, and permissions. Everything autosaves.
Finance
Review pivot tells you at a glance who's ready to bill, who's pending, and who you need to chase.
Make it fit your team
Rules and attributes that match how your business already tracks work.
Worklog rules & permissions
Description required, min/max duration per entry, daily cap, future dates allowed, max past days. Plus admin and approver permission lists. Every change autosaves.
Custom attributes
Text, number, select, checkbox, or date. Mark them required, set defaults, optionally show on the calendar card. Capture whatever your billing or compliance flow needs.
Lives on every Jira issue
Log time without context-switching. Filter your backlog by account.
Account is a real Jira field
The Account custom field is searchable in JQL with autocomplete. Build a filter for “all open issues on accounts I lead” the same way you build any other JQL query.
Why Aevon, not the other Jira timesheet apps?
| Aevon Timesheets | Other Jira timesheet apps | |
|---|---|---|
| Where does it run? | Inside Atlassian (Forge) | On the vendor's external servers |
| Does data leave Jira? | Never | Yes |
| Approval workflow included? | Yes, built-in | Add-on or missing |
| Per-account approver routing? | Yes — one week can route to many approvers | Single approver, or manual handoff |
| Billing-prep view + audit trail? | Yes (Review pivot, locked approved hours) | Reports only, manual export |
| Price per user / month | $0.50 (free 1–10, $0.25 at 1001+) | $1.50 – $5+ |
Forge-native by default
Aevon runs entirely on Atlassian's infrastructure. No external servers, no third-party processors, no separate vendor security review. Your worklog data, approvals, and audit trail stay where the rest of your Jira data lives.
Pricing that scales with your team.
Free for teams up to 10 users. Then $0.50 per user per month — roughly 1/10 the cost of incumbent Jira time trackers.
You pay
$20.00 / month
≈ $0.40 per user / month effective
1 – 10 users
Free
11 – 1,000 users
$0.50 / user / mo
1,001+ users
$0.25 / user / mo
Annual billing 16% off. Forge / Jira Cloud only. Final Marketplace tier pricing may vary at smaller tiers — see the listing for the exact tier table.
All features included at every tier. No add-ons, no per-seat-of-pain pricing.
Comparing us to Tempo? See the full price and feature breakdown.
Frequently Asked Questions
Does Aevon Timesheets work with Jira Cloud?
Yes — Aevon is a Forge app and runs exclusively on Jira Cloud.
Where is my time data stored?
Inside Atlassian's Forge storage. Worklogs, approvals, and audit history never leave Atlassian infrastructure. No external servers, no third-party data processors.
How does timesheet approval work?
Employees log time across the week, then submit. On submit, Aevon groups the week's worklogs by account (or by project when no account is set) and creates one approval request per group. Each request routes to its own approver, and the week as a whole is approved only when every request is approved. Approvers see one inbox grouped by submitter; rejecting any request requires a comment and sends the week back to draft.
Can a single week be submitted to multiple approvers?
Yes — and this is the default behavior, not a special case. A week is split into groups: worklogs logged against an account go to that account's default approver; worklogs logged against a project with no account fall back to the last approver used for that project, then to the project lead. The employee can override any group's approver before submitting via a "Change" button next to each group. A person logging time across three accounts owned by three different finance leads will, by default, send each lead only the worklogs they're responsible for.
Can employees take back a submitted week?
Yes — the Recall button puts a submitted week back into draft state as long as no approver has decided yet. Useful when you spot a mistake right after hitting submit.
Is there an audit trail of approved time?
Yes. The Timesheets Review view (admin-only) pivots every account's hours across approval states — Ready to Bill, Pending, Rejected, Not Submitted — for any date range. Each approval request stores who approved, when, and any rejection comment. Approved worklogs are locked from edits and can be exported to CSV for downstream invoicing or audit evidence.
Can we customize what employees must capture per worklog?
Yes — Settings has worklog rules (description required, min/max duration, daily cap, past/future limits) and Custom Attributes (text, number, select, checkbox, date — optionally shown on the calendar card).
How does Aevon Timesheets compare to other Jira time tracking apps?
Most competing apps are Connect-based, meaning your worklog data is sent to the vendor's servers. Aevon is Forge-native — data stays inside Atlassian. Approval workflow with per-account routing, billing-prep review, audit trail, and custom attributes are all in the base product rather than charged as add-ons. The result is a focused, integrated time → approve → bill loop at roughly 1/10 the cost of leading alternatives at 100-user scale.