A client has 120 hours. You find out at 118. By then the only conversation left is the awkward one. What you want is a warning at 80 or 90 percent, early enough to talk about scope, a change request or a pause.

Jira tracks the hours, but it has no concept of a budget, so there is nothing to alert on out of the box. Here is what you can build with the built-in tools, and where each option stops.

Step 0: decide what the budget is

Before any tool, write down three things per client: the number (hours or money), what it covers (a project, an epic, a version), and the period (one-off, or resets every month). Every option below breaks if this is vague.

Native option 1: time tracking fields and a filter

Each work item has Original estimate, Remaining estimate and Time spent. A filter such as project = ACME shown as a list with the Time Spent column, plus a subscription, gives you a regular email with the work items.

Limits: the filter lists work items, it does not total the hours. It knows nothing about a budget, so it cannot tell you that you passed 80 percent. A subscription sends on a schedule whether or not anything is wrong.

Native option 2: Automation with a scheduled rule

This is the closest native approach.

  1. Create a rule with a Scheduled trigger (daily is plenty).
  2. Add a Lookup work items action with JQL for the client's scope, for example project = ACME AND worklogDate >= startOfMonth().
  3. Add a Send email or message action that goes out when the hours cross a threshold you typed into the rule.

The sum is where it gets rough. Smart values can read time spent per work item, and in a scheduled rule you can add them up across the lookup results, but check the output on a real run before you trust it: time spent on a work item covers all dates, not just the current month, so a monthly budget needs care. The threshold lives inside the rule, so every client is a copy of the rule to edit.

Limits:

  • Hours only. Money needs rates, and dated rates are awkward to keep inside a rule.
  • One rule per client or budget, with the number hard-coded.
  • Rule runs count towards your plan's Automation usage, and a lookup over a large project is slow.
  • It tells you the threshold was crossed. It does not tell you when the budget will run out at the current pace.

Native option 3: a spreadsheet

Export the worklogs (author, date, time), sum per client, compare with the budget in a column, and colour the cell when it passes 80 percent. This is honest and works, as long as someone refreshes it. In practice the export gets a week old, and the alert is a person remembering to open the sheet.

What a good warning needs

  • A budget with a number and a period, not a threshold buried in a rule.
  • Spend that is always current, with rates when the budget is money.
  • A pace, so "80 percent used" can be read as "11 days left" or "fine until the end of the month".
  • A status you can scan across all clients in one place.

Burnrate

Full disclosure: we build Burnrate. Burnrate for Jira reads the worklogs your team already logs, prices them with a dated rate card and compares them with budgets that you create per project, epic, fix version or JQL query, in money, hours or both, one-off, monthly or quarterly.

What it gives you for this problem:

  • A warning level per budget (80 percent by default). When usage reaches it, or the forecast says the budget will be exceeded, the budget shows as At risk. Past the limit it shows Over budget; otherwise On track.
  • A forecast next to the status: pace over the last 28 days, a projected total for the period and, when it falls inside the period, the day the budget runs out. How that is calculated is in the burn rate article.
  • All budgets in one list, so you see which clients are at risk without opening a sheet.

What it does not do: it does not email or message you when a budget turns At risk, and there is no dashboard gadget yet. You see the status when you open Burnrate. If you want a push, a team routine that opens the budget list every Monday does the job, and a native Automation rule on hours can sit next to it as a backstop.

For two or three clients with hour budgets, an Automation rule per client is fine. When there are many budgets, some in money, some resetting monthly, a status that is always current is the part worth handing over.

Jira and Atlassian are trademarks of Atlassian. Kayabyte is independent and not affiliated with or endorsed by Atlassian.