FAQ
Common questions about Aevon Timesheets.
Product & platform
Does Aevon work with Jira Cloud?
Yes — Aevon is a Forge app and runs exclusively on Jira Cloud. Jira Server and Data Center are not supported.
Where is my time data stored?
Inside Atlassian's Forge storage. Worklogs, approvals, and audit history never leave Atlassian's infrastructure — no external servers, no third-party data processors. Worklogs themselves are stored as native Jira worklogs, so they're also visible on each issue's Work log tab.
How does Aevon 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, so data stays inside Atlassian. The approval workflow, per-account routing, billing-prep review, audit trail, and custom attributes are all in the base product rather than charged as add-ons — a focused time → approve → bill loop at roughly 1/10 the cost of leading alternatives at 100-user scale. See the overview comparison.
What does it cost?
Free for 1–10 users, $0.50/user/month for 11–1000 users, and $0.25/user/month (flat) at 1001+ users.
Logging time
What are the ways to log time?
Click Log Activity or an empty slot on the calendar, use the "+" on a day header, drag an issue from the sidebar, run the timer, or log from the issue panel on any Jira issue.
Can I log time for someone else?
Aevon is built around logging your own time — you submit your own week for approval. Time is logged as the current user.
Can I require a description or limit durations?
Yes — worklog rules let an admin require a description and set minimum, maximum, and daily-cap durations, plus past/future time-window limits.
Can I capture custom data per worklog?
Yes — custom attributes add extra per-worklog fields in five types (text, number, select, checkbox, date), optionally required and optionally shown on the calendar card.
Approvals
How does timesheet approval work?
You 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 is approved only when every request is approved. See Submitting timesheets.
Can a single week go to multiple approvers?
Yes — and it's the default, not a special case. Each account's worklogs route to that account's default approver; project worklogs with no account fall back to the last approver used for that project, then the project lead. You can override any group's approver before submitting.
Can I take back a submitted week?
Yes — the Recall button returns a submitted week to draft, as long as no approver has decided yet. See recalling a submission.
What happens when an approver rejects?
A rejection requires a comment and sends the whole week back to Draft so you can fix it and resubmit. See Approval statuses.
Billing & audit
Is there an audit trail of approved time?
Yes. The Billing review view (for reviewers and admins) pivots every account's hours across approval states — Ready to bill, Pending, Rejected, Not submitted — for any date range. Each approval request records who approved, when, and any rejection comment. Approved worklogs are locked from edits and can be exported to CSV.
Can I export for invoicing?
Yes — Reports exports Pivot and Raw CSV, and Billing review exports approved-only or all worklogs for a range.
How do I make approved weeks truly immutable?
Within Aevon, submitting a week locks all of its worklogs from the owner's edits, and approving makes that lock effectively permanent. But Aevon enforces this lock only through its own resolvers — a user who holds Jira's native Edit Worklog or Delete Worklog permission can still modify a worklog by calling the Jira REST API directly, since Jira has no concept of Aevon's period lock. For hard, audit-grade immutability, revoke Edit Own / Edit All Worklogs and Delete Own / Delete All Worklogs from the relevant roles in Jira → Project settings → Permissions (or your global permission scheme).
Administration
Do I need to be a Jira admin?
A Jira administrator is needed for the initial install. After that, Jira site admins are always Aevon admins, and you can grant the Aevon admin or account administrator roles to others. See Permissions.
Who can administer Aevon on a fresh install?
Whoever installed it. A Jira site administrator always has full Aevon access and can never be locked out, so there's no step to "claim" admin. Grant roles to others in Jira → System → Global permissions. On a fresh install, members of the jira-administrators group already hold the Aevon admin, account-admin, and reviewer roles by default. See Permissions.
Why doesn't the Account field show on my issues?
The site-wide Account custom field isn't added to project issue screens automatically — that's a Jira platform constraint. A project admin adds it under Project settings → Issues → Screens.