Docs / Start

Quick start

Create a cost project, set rates and see real numbers in about ten minutes. The same example is used throughout these docs.

The example project#

These docs use one small project so the numbers can be followed from page to page. You do not need the same data; any Jira space with a few worklogs will do.

Example: Website redesign

A monetary project in USD that reads the Jira space WEB. Three people logged time in July 2026:

PersonSet up asHours logged
AnnaOwn rate 50/h10 h
BenRole "Developer" at 40/h5 h on a CAPEX issue, 5 h on other issues
CarolNo rate of her own, no role4 h

The project default rate is 30/h, and a cost account "Capitalised work" (JQL labels = capex) has a rate of 60/h.

Create the project#

  1. Open Cost Tracker from the Jira Apps menu and choose Create project.
  2. Give it a name and a scope: pick the Jira space WEB, or write a JQL filter. The scope is checked against your site before it is saved.
  3. Choose the project type. Monetary-based computes cost and budget in a currency from hourly rates. Time-based uses hours only and no rates. You can change this later, but nothing is converted (see changing the type or currency).
  4. Set the currency (USD) and, under Settings → Rates and revenue, a Default hourly rate of 30.

Do not skip the default rate. A new monetary project starts with a default rate of 0, so time is counted but priced at 0 until some rate applies. The app shows an "Hourly rates are not set" banner on Overview, Team and Revenue while this is the case.

Set rates#

  1. Open the Team tab. Everyone who logged time in the scope is already listed.
  2. In the Roles card, add the role Developer with a cost rate of 40, then give Ben that role in the table.
  3. For Anna, open the ··· menu on her row, choose Edit cost rate and history and enter 50. Leave Effective from empty for now.
  4. Create the cost account (a Jira administrator does this under Accounts): name "Capitalised work", JQL labels = capex, cost rate 60.

Check the result#

Each worklog takes the first rate that applies, in this order: the person's own rate, the cost account's, the role's, then the project default. For the example:

WorklogRate usedWhyCost
Anna, 10 h50Her own rate wins over everything500
Ben, 5 h on a CAPEX issue60He has no own rate, and the account's rate beats his role300
Ben, 5 h on other issues40No own or account rate, so his role applies200
Carol, 4 h30Nothing else matches, so the project default applies120
Labor cost1,120

Open Overview and Team to see the same figures. If cost shows 0, see Troubleshooting.

What to add next#

Cost Tracker is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. Questions or corrections: info@vudia.site.