A budget per project, and the cost of the work logged on it.

Open the project, click Budget & Cost in the sidebar and fill in the form:

• Budget amount, for example 25000 or 25,000.50. Commas between thousands are fine. A comma as the decimal mark (25000,50) is refused rather than misread.
• Currency: AED, AUD, BRL, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, KRW, MXN, MYR, NOK, NZD, PHP, PLN, SAR, SEK, SGD, THB, TRY, USD or ZAR. JPY, KRW, HUF and IDR take whole amounts only. Currencies with three decimals are not offered.
• First month (YYYY-MM). Work logged from this month on counts.
• Last month (YYYY-MM, optional). Leave it empty for a budget with no end month.

Click Save budget. The app starts reading the project's work logs at once. Until the first read is done, the page says the numbers are not complete yet.

Change budget opens the same form. Changing the currency does not convert the budget or the expenses already entered; their numbers stay the same. If the new first month is earlier, the app reads the project's work logs again from that month.

Remove budget asks first, then deletes the budget and its expense lines at once, and the hours the app has read for the project at the next sync. Work logs in Jira are not changed.

If someone else changed the budget since your page loaded, the save is refused with a message and a Reload button, so one person's change never silently overwrites another's.

Under Expenses, a project administrator or Jira admin fills in Date (YYYY-MM-DD), Description and Amount, then clicks Add expense.

• The date must fall in the budget months. Each line counts in the month of its date.
• A minus amount is a refund.
• Descriptions are up to 200 characters. A project can have up to 1,000 lines; fewer if the descriptions are long.
• The table shows Date, Description, Amount and Added by. If you later change the budget months so a line falls outside them, it is marked not counted: outside the budget months.
• Delete asks first. A deleted line can't be brought back.

• Which rate. A personal rate wins. Without one, the app uses the highest rate among the groups with a rate that the person is in. A rate applies from its start month until a newer rate for the same person or group starts. Before a person's first personal rate starts, their group rate applies.
• Which month. A work log counts in the month of its start date, as Jira gives it to the app. Work that runs past midnight at the end of a month counts fully in the month it started.
• The sum. Cost is hours times rate, per person and month, rounded to the cent (to the whole unit for JPY, KRW, HUF and IDR). Hours without a rate are shown and not counted.
• Spent is work cost plus expense lines, in the budget months. Used is rounded down to 0.1%, so 79.96% shows as 79.9% and never as 80% before the note.
• Currency. Rates are plain numbers, read in each project's currency. There is no currency conversion: if projects use different currencies, the same rate is read as a different currency in each.
• Groups. Members are read as they are now, because Jira keeps no history of group membership. A person who leaves a group loses its rate for past months too. Give them a personal rate to keep it.

Costs are worked out each time a page opens, from the stored hours and the current rates. They are never stored, so a rate change shows at once.

When a budget is saved, the app reads every work log in the project from the first month on. After that it reads, every hour, only the work logs changed or deleted since the last read. It also reads the members of every group that has a rate.

• A sync also starts when a budget's first month moves earlier, when a group gets its first rate, and when someone clicks Sync now. If one of these happens during a sync, another sync runs when it ends.
• Jira lists a change to a work log about a minute after it is made, so a change from the last minute shows at the next read.
• Read all work logs again forgets the hours read for the project and reads them all again. Use it after issues are moved into or out of the project. Until it finishes, the numbers are not complete.
• If a sync makes no progress for 20 minutes, the button becomes Restart the sync.
• If Jira refuses to show some work logs, or a project can't be read (for example it was deleted or archived), the page says so. The other projects still sync, and the next sync tries again.
• On a site whose subscription or trial has ended, the hourly sync stops. It picks up again when the licence is active.

• Restricted work logs. Jira only returns work logs the app can see. Work logs limited to a group or role the app is not in may be left out. The page says when Jira refused some.
• Moved issues. Moving an issue to another project doesn't change its work logs, so the app doesn't see the move until one of them changes. Read all work logs again fixes it.
• Deleted issues. Jira may not report the work logs of a deleted issue as deleted. If it doesn't, they stay counted until Read all work logs again.
• Past group membership. Jira keeps no history of it, so group rates follow today's members.
• Mid-month rate changes. Rates apply by whole month.
• Deleted groups. If a group with a rate is deleted, its rate stops applying. Deactivated people stay in their groups and keep their rates.
• Not in this version: budgets per epic, currency conversion, rates per project, and emails or Jira notifications when a budget passes 80% or 100%.
• Numbers are at most about an hour old, unless someone clicks Sync now.