Docs / Reference

Limits and behaviour

Every limit and fixed behaviour in one place: sizes, caching, formats and what happens at the edges.

Limits#

WhatLimitWhat happens at the limit
Issues read per cost project500The page says "first 500 of about N issues" and the totals are incomplete. Split the project (below).
Cost accounts on the site20Creating a 21st is refused. Each account costs an extra Jira search per project calculation.
Role name length60Refused. Names must also be unique within a project, ignoring case.
Milestones per project24Refused.
People named in a project's sharing50Refused.
Calculated figures are kept~15 minRecomputed after that, or immediately after a change that affects them.

If a project is over 500 issues#

The 500-issue limit is deliberate, sized for small and medium teams. A bigger scope still works, but only the first 500 issues count and the page says so (Overview, Scope and Reports all show the warning, with the real size when Jira can tell). To get complete figures:

Behaviour#

TopicHow it behaves
CurrencyA property of each project. Amounts are never converted. A portfolio or report adds money only across projects with the same currency.
RatesNon-negative numbers. Empty means "use the next level", 0 is a real rate. A rate can start on a date; with no date it applies to all hours.
Worklog dateThe day the worklog was logged for, as Jira stores it. Rates are matched to this date.
Type or currency changeNothing is converted; the app asks you to confirm first.
Date formatShown in Jira's own style, for example Oct 22, 2026. Typed dates also accept YYYY-MM-DD.
ReportsRead Jira live (not cached) for the chosen timeframe.
ExportsXLSX files, generated from what is on screen. CSV export was removed.
Jira dataOnly read, never changed. See Privacy.
Cost Tracker is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. Questions or corrections: info@vudia.site.