Skip to main content

Getting Started

This guide takes you from installation to your first submitted week. The whole process takes about 10 minutes.

Prerequisites​

  • A Jira Cloud instance (Aevon is a Forge app and runs only on Jira Cloud)
  • Jira administrator access (for installation and time-tracking setup)

Step 1: Install from the Marketplace​

  1. Open the Atlassian Marketplace and search for "Aevon Timesheets"
  2. Click Get it now and select your Jira instance
  3. Review the permissions and click Install

Aevon installs as a global app. After installation you'll find it in the Jira navigation under Apps → Aevon Timesheets, and an Aevon Timesheets panel appears on every Jira issue.

Start from the in-product Get Started hub

Jira admins also get a Get started hub at Manage apps → Aevon Timesheets → Get started — a one-page checklist with one-click buttons for the steps below (set the time-tracking provider, read the docs, add your team, start logging time). You can return to it anytime.

Aevon Timesheets Get Started hub

Step 2: First launch​

On first launch, Aevon shows a welcome screen with quick links into the calendar, reports, and approvals.

Aevon Timesheets welcome screen

You already have admin access

As the person who installed Aevon, you're a Jira site administrator — which always means full Aevon access. Site admins can never be locked out, so you can head straight to Settings to configure the app.

Step 3: Set Aevon as your time tracking provider​

Aevon registers itself as a Jira time tracking provider. Selecting it routes Jira's built-in time-tracking surfaces — the time-tracking field and Log work action on each issue — through Aevon. Your worklogs are always stored as native Jira worklogs, so this only changes which engine Jira's native UI uses; it never moves or hides existing data.

  1. In Jira, open Settings (⚙) → Issues
  2. Under FEATURES in the left sidebar, select Time tracking
  3. Make sure time tracking is on
  4. In the Time tracking provider dropdown, choose Aevon Timesheets
  5. (Optional) Set the working hours per day, days per week, and default time format
  6. Click Save

For the full reference on these settings, see Atlassian's Configure time tracking guide.

Step 4: Grant roles to your team​

Jira site administrators are always Aevon administrators, so you don't need to grant yourself anything. All Aevon roles are managed in Jira → System → Global permissions:

  1. Go to Settings (⚙) → System → Global permissions
  2. Find Aevon Administrator, Aevon Account Administrator, or Aevon Reviewer
  3. Add the Jira group that should hold the role, then click Add

All three roles default to the jira-administrators group, so your Jira admins already have them. See Permissions for the full role model.

Step 5: Create an account (optional)​

Accounts are cost centres that let you route hours for billing. You can skip this and log time straight away, but if you bill or do chargeback, set them up now:

  1. Go to Accounts
  2. Click + Add account, give it a name, pick a category (Billable, Capitalized, Operational, or Internal), and choose a default approver
  3. (Optional) Under Account routing, set a default account per project so worklogs are routed automatically

See Accounts and Account routing for details.

Step 6: Log your first worklog​

  1. Open Aevon Timesheets from the Jira navigation — you'll land on the weekly calendar
  2. Click Log Activity (or click any empty slot on the grid)
  3. Pick an issue, set the date, start time, and duration, add a description, and click Log work

Your worklog appears as a card on the calendar. You can drag it to a different time, resize it to change the duration, or click it to edit. See The weekly calendar and Log Work dialog.

Faster ways to log

Start a timer from the Work Items sidebar, drag an assigned issue onto the grid, or log directly from the issue panel on any Jira issue.

Step 7: Submit your first week​

When your week is complete:

  1. Click Submit week in the calendar header
  2. Review the approval groups — Aevon splits the week by account (or by project when no account is set) and routes each group to an approver
  3. (Optional) Click Change on any group to pick a different approver
  4. Click Submit

The week moves to Submitted. Your approver sees it in their Approvals inbox, and you can track each approver's decision — or recall the week — from Approvals → My submissions.

What's next​

  • Core Concepts — understand worklogs, periods, accounts, and routing
  • Time Tracking — every way to log and rearrange time
  • Approvals — the full submit, approve, and recall flow
  • Administration — configure rules, attributes, and permissions
Add the Account field to your issue screens

If you want per-issue account overrides, a project admin must add the Account custom field to that project's issue screens. See Account custom field.