Cost accounts

Named buckets of work, such as CAPEX and OPEX or a client, defined by JQL, that can carry their own rates and receive expenses.

A cost account groups work for cost purposes: capitalised versus operating spend, a client, a cost centre. Unlike a Jira custom field, an account is defined by a JQL filter, so no field has to be added to your issues.

What an account holds#

How an account is applied to a project#

• For each project, the account's JQL is combined (AND) with the project's own scope, and the matching issues are found in the same scan that computes the report.
• An account's rate applies to work on its issues. It beats a role's rate and the project default, but not a person's own rate.
• An issue that matches more than one account goes to the account created first, so every worklog has exactly one rate.
• If an account's JQL later stops being valid (a deleted field, for example), the account is skipped rather than breaking the report.
• Account rates are plain numbers applied as-is in each project's own currency. There is no conversion.
• Expenses can be booked to an account, which is how the Overview's Accounts card and the "by account" report split cost.

Who can manage accounts#

Accounts are site-wide setup, like attributes and the role library. Only Jira site administrators can create, edit or delete them; everyone can see them. Accounts are managed under Setup → Accounts, with a switch between Accounts and Customers views.