Skip to main content

Troubleshooting

Solutions to the issues people hit most often.

The Account field doesn't appear on my issues​

Symptom: You set up accounts but the Account field isn't on your issues, so you can't set a per-issue override.

Cause: The site-wide Account custom field is not added to project issue screens automatically — a Jira platform constraint.

Fix: A project admin adds the Account field under Project settings → Issues → Screens for the relevant screen(s). Until then, time still routes via the project default account.

A worklog routed to the wrong account​

Symptom: Time landed on a different account than expected.

Cause: Routing follows a precedence waterfall: the issue's Account field wins, then the project default, then none.

Fix: Check whether the issue has an Account field value (it overrides the project default), then check the project default. Adjust whichever one is steering the result.

I can't edit a worklog​

Symptom: A worklog won't save changes, or drag/resize is rejected.

Causes & fixes:

  • You've submitted the week. Submitting locks every worklog in the week from your edits — even before an approver acts. Recall the week (while no approver has acted) or have an approver reject it to return it to Draft.
  • A worklog rule blocks it — e.g. a missing required description, a duration outside the min/max, or a date outside the allowed time window. The error banner names the constraint.
  • A Jira permission issue on the underlying worklog. Confirm you can edit worklogs on that issue in Jira.

My submission isn't showing up for the approver​

Symptom: You submitted a week but the expected approver doesn't see it.

Cause: Each group routes to a specific approver — the account's default approver, or (for no-account project work) the last approver used for that project, then the project lead.

Fix: In Approvals → My submissions, check the per-approver chips to see who each group actually routed to. If it's wrong, recall the week and use Change on the group to pick the right approver before resubmitting.

A teammate can't open Settings, Accounts, Approvals, or Billing review​

Symptom: Someone gets an Access denied screen on a restricted view.

Cause: Those views are role-gated. Calendar and Reports are open to everyone; Approvals needs an approver or admin, Billing review needs a reviewer or admin, Accounts needs an account admin or admin, and Settings needs an admin.

Fix: Grant the right role (Aevon Administrator, Account Administrator, or Reviewer) to a Jira group in Jira → System → Global permissions — or make them a Jira site admin, which always has full access. See the permissions matrix.

More people have admin access than expected​

Symptom: People you didn't explicitly grant a role can still reach Settings, Accounts, or Billing review.

Cause: Two built-in grants. Jira site administrators always have full Aevon access (it can't be removed inside Aevon). And on a fresh install the Aevon Administrator, Account Administrator, and Reviewer global permissions are granted by default to the jira-administrators group, so every member of that group holds those roles.

Fix: Adjust the group grants in Jira → System → Global permissions, and review who's a Jira site administrator. See Permissions.

The timer disappeared after a reload​

Symptom: You expected a running timer but don't see it.

Cause: The timer is hidden when idle, and its state lives in your browser's local storage.

Fix: A reload in the same browser keeps the running timer. The timer doesn't follow you to a different browser or a private window, since the running state is stored locally. See Timer.

A report looks like it's missing days or rows​

Symptom: The Reports pivot seems to cut off.

Causes & fixes:

  • Date columns scroll horizontally — a long range has more columns than fit; scroll right to see the rest.
  • A filter is active — check the Filter by footer for active filters and Clear all if needed.
  • The date range is too narrow — widen it to include the worklogs you expect.

Getting help​

When reporting an issue, include the steps to reproduce, what you expected versus what happened, your browser, and any error banner text.