Radrly
CapRadar
Try it free

Documentation

Everything you need to install, configure and use CapRadar.

Documentation version 1.11, updated 26 October 2026. It describes the CapRadar code running in production (Forge app version 2.35.0).

Overview

CapRadar is an Atlassian Forge app for Jira Cloud. It classifies the hours in Jira worklogs as CapEx, OpEx, Excluded or Unclassified, records R&D qualifying time, and runs a period close with pre-close checks, approval and lock, with a hash-signed snapshot in the Advanced edition. Exports include a CSV pack, a journal entry file, a board pack and, in Advanced, an auditor PDF, all built in your browser.

CapRadar supports your accounting and tax process and collects evidence for it. It does not give accounting, tax or legal advice. Every capitalization or tax decision (what to capitalize, from when, at what rate) stays with you, your auditor and your advisors.

Requirements

  • Jira Cloud. A Jira administrator installs CapRadar. Jira administrators are always CapRadar finance admins.
  • Jira groups (optional) for the CapRadar roles: finance admin, approver, reviewer, engineering manager, auditor and viewer.
  • Worklogs in Jira: written in Jira, by a time tracker that writes native worklogs, or by Tempo. Timesheet-free allocation also reads assignees, resolution dates, story points and status history.
  • Cost rates by person, role, team or space, as a CSV file.
  • Rovo only for the Rovo agent (Advanced). Every other feature works without it.

Install and get started

  1. Install CapRadar from its Atlassian Marketplace listing. A Jira site administrator approves the four read and storage scopes.
  2. Open the admin page (Jira settings → Apps → CapRadar; Get started and Configure open the same page). Start the 24-month backfill and enter the Jira group names for the CapRadar roles. The page also shows sync status and what CapRadar stores.
  3. Check the default policy on Policies: standard, currency, measurement method and default treatment. On Calendars, set the fiscal year, the working week, hours per day and the public holiday country.
  4. Import rates on Rates.
  5. Add rules, for example Stories in space PAY as CapEx, Bugs as OpEx, label maintenance as OpEx. Preview each rule with the simulator before you save it.
  6. Clear the queue. To classify lists the unclassified hours by epic. Add a rule, an override or a phase for the largest items.
  7. Close the period on Close & sign: prepare, resolve or waive the checks, then approve and lock. Download the packs from Exports.

CapRadar supports Jira's light and dark themes.

Sync and read-only mode

  • CapRadar follows worklog created, updated and deleted events, and an hourly reconcile catches anything an event missed.
  • The backfill imports worklogs from the last 24 months. Start it on the admin page; it is safe to run again.
  • A daily job rebuilds the totals of open periods.
  • Jira does not always say which space a worklog belongs to. CapRadar then takes the space from the work item, and the hourly reconcile and the daily job correct worklogs that were saved without a space and rebuild the totals of the periods concerned. Signed snapshots are not changed, so a locked period keeps the values it was signed with.
  • If the hourly reconcile fails, or has not succeeded for six hours, CapRadar becomes read only: you can read everything, and saves are blocked until the next successful reconcile. A banner says so.

Measurement methods

CapRadar measures work with three methods, all inside Jira. Period totals, the close, the snapshot and the journal use worklogs (methods a and b). Allocation and imported attribution are shown next to them, so hours are never counted twice. The Overview shows the method mix for each period.

(a) Attributed worklogs
Native Jira worklogs with an author, written in Jira or by time trackers that write attributed native worklogs.
(b) Tempo sites
When Tempo writes a worklog, the Jira copy does not identify the person. CapRadar reports those hours per work item, epic and space, costs them with the space blended rate, and labels them “no per-person attribution”. In Advanced you can import a Tempo report CSV (person, work item, date, hours) or a percentage CSV (person, epic, month, share), labelled “imported attribution” and shown on Attribution, in R&D packs and in the method mix.
(c) Timesheet-free allocation
A finance admin computes one open month on the Allocation screen. Two bases are available: resolved work items (each person's working hours split across the work items they resolved that month, by story points or by count) and in-progress days (each working day split equally across the work items assigned to the person in an In Progress status, read from the Jira changelog, net of holidays and absences). Days without an in-progress work item stay unallocated. The changelog is read up to 200 events per work item.

The method calibration report compares allocation (c) with attributed worklogs wherever both exist, per person, epic and class, so you can show your auditor how close the allocation is.

Hierarchy

CapRadar uses the Jira hierarchy through the parent field: initiative, epic, work item and subtask. A work type whose name contains “Initiative” marks the initiative level.

Rates and cost

  • Person, role, team and space rates, effective-dated, in the policy currency, imported by CSV. A file is saved completely or not at all. The columns are scope,target,hourly_cost,currency,effective_from,effective_to with optional loaded_multiplier and monthly_cost, or a role file role,rate_per_hour,currency,valid_from. A person can be named by account ID or email; an email is resolved at import and not stored.
  • Rate order: the person's rate, then their role rate, then the rate of the team with the largest share, then the space blended rate. Tempo hours use the space rate.
  • Cost methods: hours multiplied by the rate and the optional loaded multiplier, or (Advanced) monthly cost multiplied by the share of the period's expected working hours.
  • Rates and cost are visible to finance roles only, enforced on the server.

Policies and templates

A policy holds the accounting standard and its phase set, the currency, the measurement method, the cost method, the default treatment and its rules. Every space uses the default policy unless it is assigned to another one. Templates give you a starting point:

Policy templates
TemplatePhasesDefault treatment
US GAAP, ASC 350-40 (stage model)Preliminary, Application development, Post-implementationOpEx, CapEx, OpEx
US GAAP, ASU 2025-06Not yet probable, Probable to complete, Complete or in useOpEx, CapEx, OpEx
US GAAP, ASC 985-20 (software to be sold)Before technological feasibility, After technological feasibility, Available for saleOpEx, CapEx, OpEx
IFRS, IAS 38Research, Development, In useOpEx, CapEx, OpEx
CustomThe ASU 2025-06 phase set as a starting pointOpEx, CapEx, OpEx

ASU 2025-06 removes the project stages from ASC 350-40 for internal-use software. It is effective for annual reporting periods beginning after 15 December 2027, with early adoption permitted.

Policies are versioned. Each save appends a version with a reason in the audit trail. A version holds the name, standard, currency, measurement method, default treatment and cost method: hourly, or monthly share in Advanced (when no cost method is sent, the version keeps the current one). Open periods are classified again on the latest version. A locked snapshot keeps the policy hash it was closed with. Advanced adds more policies (each with its own standard and currency, and spaces assigned to them), a diff between two versions and a simulation of a move to another standard; neither the diff nor the simulation writes anything. Amounts are not converted between currencies: a space whose policy uses a different currency from the default policy keeps its hours and stores no cost.

Rules

A rule is a set of conditions plus an outcome. Conditions are combined with AND within a rule and OR within one dimension.

  • Conditions on the Rules screen: space key, work type, label, component, custom field (customfield_N=value) and a JQL subset (project, key, issuetype, labels, component, epic and custom fields, with =, !=, ~, IN, NOT IN, IS EMPTY, AND, OR, NOT and parentheses), evaluated on the fields CapRadar stores. Rules drafted by the Rovo agent can also use the epic phase.
  • Outcomes: a treatment (CAPEX, OPEX, EXCLUDED) and, independently, an R&D flag and (Advanced) an R&D category.
  • Priority: an explicit number; the higher number wins. Ties go to the more specific rule, then the older rule.
  • Policy: rules are saved on the policy selected on the Rules screen, and each space is classified with the rules of its policy.
  • Saving: Add rule saves the rule on the selected policy and classifies open periods again. If that reclassification is busy, it continues in the background and the rule is still saved.
  • Versioning: rules are never edited in place. To change an outcome, add a rule with a higher priority. Every result records the rule ID and version.

Resolution order

  1. Override on the worklog
  2. Override on the work item
  3. Class of the parent work item (for subtasks), when it is classified
  4. Override on the epic
  5. Override on the initiative
  6. ASU 2025-06 gate on the epic's phase: work before the funding authorization date, or inside the uncertainty window, is OpEx
  7. Highest-priority matching rule
  8. Treatment of the epic's phase on the work date
  9. Policy default (UNCLASSIFIED by default, so nothing is capitalized by accident)

Every result stores why it was classified that way. The work item panel and the Rovo agent show the decision path, for example the epic an override came from or the rule and its priority.

Rule simulator

Before you save a rule, the simulator runs it against up to 1,500 worklogs of the selected period and shows the matches, the hours that change class and the change in CapEx cost. Nothing is saved until you confirm. Saving a rule classifies open periods again; locked periods are never changed by a new rule.

Capitalization phases

Set the phase of an epic with an effective date and an optional evidence note, for example “Board approval 12 March 2026”. The policy's standard decides what each phase means. Phases are shown by name in your language, for example Probable to complete, never as internal codes. Work without an epic uses the phase of its initiative.

For ASU 2025-06, each phase row can carry a funding authorization date and a significant development uncertainty window (from and to). Work before the authorization date, or inside the uncertainty window, is OpEx with the reason shown. A pre-close check warns about CapEx epics without an authorization date.

Phase changes are audited. They apply to open periods; a locked period keeps its snapshot until it is reopened. Saving the same phase again for an epic (same phase, effective date, funding date and uncertainty window as its latest row) writes nothing new. Dates, letter case and spaces are compared after normalising, and a blank evidence note means no new evidence, so the note already stored is kept. A different note is saved as a new row. The phase history shows the evidence note of each row.

Overrides

  • Override a worklog, work item, epic or initiative with a treatment, an R&D flag, a reason of 10 to 500 characters and an optional reference (ticket or memo ID). The target must already be in CapRadar.
  • Overrides are set by finance admins on the Overrides screen, or applied from an AI suggestion or a confirmed Rovo action.
  • The R&D flag on an override decides the R&D result for its target: on marks the hours as qualifying, off marks them as not qualifying. The Overrides list shows the flag.
  • A target has one override per level. Saving an override for a level and target that already has one replaces it: the dialog says Update override and shows the override it replaces. The replaced override is kept in the audit trail, and the Overrides list shows only the current one.
  • Every override is in the audit trail.

To classify and coverage

To classify lists the unclassified hours of a period grouped by epic (or by work item when there is no epic), with the space, hours, worklogs, people and a Tempo marker. Overview shows the share of hours still to classify. Allocation and imported attribution are not part of the queue. Classify the rows with a rule, an override or a phase.

The coverage check (Advanced) compares each person's logged hours with their expected hours (working days times hours per day, net of holidays and absences) and flags anyone under 80% or over 120%. It lists people who have hours in the period, by their Jira display name; Tempo hours have no person and are not compared.

Calendars and organisation

  • Fiscal calendar: fiscal year start month and calendar months or 4-4-5, 4-5-4 and 5-4-4 week patterns, with fiscal year, period and quarter labels. In a week pattern the last period takes any remaining days, so the year is fully covered.
  • Working calendar: working week, hours per day and bundled public holidays for the United States, England and Wales, Poland and Germany (nationwide holidays). Absence import (person,from,to,type,share) is Advanced. Allocation, coverage and monthly share costing use the calendar.
  • Organisation dimensions: effective-dated cost centre, department and legal entity per person, imported by CSV and shown on the Organization screen and in the journal cost centre column. Advanced adds team membership with percentage shares, validated to at most 100% per person and day so time is never counted twice.

Period workflow and close

Period states
StateWhoWhat happens
OpenAutomaticWork classifies continuously; numbers can change.
In reviewFinance admin (Prepare)Pre-close checks run: unclassified hours and missing rates block the lock unless a finance admin waives them with a reason; CapEx epics without a funding authorization date are a warning. Worklogs still classify; if hours change, earlier signatures must be given again.
Reviewed (Advanced, separation of duties on)Engineering managers, then the ReviewerEngineering managers sign off the hours of each space that has hours and a delegated manager, then the reviewer signs the review step.
LockedApprover or finance admin (Approve and lock)Approval and lock are one step with an attestation. CapRadar builds the snapshot and records the signer, time, time zone, attestation version and policy hash. Later changes become post-lock adjustments in the next open period.
ReopenedApprover or finance admin, with a mandatory reasonThe old snapshot is kept and marked superseded; the next lock is chained to it.

Separation of duties is on by default in Advanced: preparer, reviewer and approver must be different people, and an engineering manager sign-off cannot come from the preparer. In Standard the default is single-person close, printed on the signature; a finance admin can switch it off so that the approver must be a different person from the preparer.

Periods are calendar months by default, or fiscal week periods when a week pattern is set. Work is assigned to a period by the worklog start time in UTC. A close of more than 20,000 lines is refused.

Snapshots, signatures and Verify Advanced

Signed snapshots, the hash chain with Verify, and the auditor PDF are part of the Advanced edition. On Standard, approve and lock still freezes the period, and the CSV pack, board pack, journal and post-lock adjustments use the locked lines, but the content hash, the chain and the signature rows are not shown and Verify is not available. Nothing is deleted, so after an upgrade to Advanced the full record of earlier locks is shown.

  • Each locked period produces a snapshot with a SHA-256 content hash. Prepare, sign-off, review and approval are stored as signature rows, each hashing the content hash and the previous signature.
  • Each snapshot carries the hash of the previous period's snapshot, so the periods form a chain.
  • Verify on Close & sign recomputes the hashes and checks every signature row. The CSV pack manifest lists the SHA-256 of every file, so an auditor can check it offline with sha256sum.
  • The hash makes any later change to a snapshot detectable. It is tamper-evident only.

Post-lock adjustments

When a worklog dated in a locked period is added, changed or deleted, CapRadar records a post-lock adjustment in the next period that is not locked, with its source period, hours and cost. A signed period is never changed. Adjustments are listed on the Overview and on Close & sign, included in the exports, and the journal books their cost as a separate balanced pair.

Reports

  • Overview: CapEx, OpEx, R&D and unclassified hours (with cost for finance roles), the method mix, totals by space with the space name and key, and the adjustments of the period, with a freshness line showing the last event and the last reconcile. When some hours have no rate, finance roles see a note with a link to Rates. A locked period reads its snapshot.
  • Organization: each person's cost centre, department and legal entity in force at the end of the month and, in Advanced, hours and cost split by team. Tempo hours have no person, so they appear as one Unattributed (Tempo) row and the team total can be lower than the Overview total.
  • Allocation and Calibration: allocated hours, and logged versus allocated hours by person, epic and class.
  • People are shown by name. Organization, Coverage, Allocation, Attribution, Calibration, R&D packs and the audit sample on Exports show each person's Jira display name, read from Jira when the screen loads. A closed account, or a name Jira cannot return, shows as Unknown user; hours with no person show as No person. The R&D pack CSV, built in your browser from the screen, carries the same names. Other exported files keep the pseudonymous person key.
  • Board pack: one PDF page for the month and the year to date: capitalization rate, rate trend, CapEx hours and cost, CapEx by initiative, adjustments, status and hash. A month without CapEx or OpEx hours shows the rate as n/a. On screen, the trend table also shows CapEx hours per month. Plan versus actual is on the Plan screen.
  • Advanced reports: Coverage, R&D packs, Amortization, Plan and Costs.

Exports

Exports
ExportContentsIntegrity
Period CSV pack (ZIP)summary.csv, lines.csv, people.csv (person keys, no names), rules.csv, audit.csv (last 90 days, up to 200 rows), journal.csv for a locked period, manifest.csv, and columns-pl.csv when the interface is in Polish. Up to 1,500 lines; the manifest says when that cap is hit.Manifest with the SHA-256 of each file, and the snapshot content hash in Advanced
Auditor PDF (Advanced)Period, status, policy, standard and method; the signature with snapshot, content hash, previous snapshot, signed time and time zone, attestation and methodology version; summary; rules; adjustments; a reproducible random sample of 25 lines with its seed; the journal; verification stepsSnapshot ID and short hash on every page
Journal entry fileBalanced debit and credit lines per class and cost centre, from a locked periodSnapshot ID in every row, and the content hash in Advanced
Board pack PDFExecutive summary for the month and year to dateSnapshot ID, and the short hash in Advanced
XLSX (Advanced)Summary, Lines and Journal sheetsDraft watermark unless the period is locked
ERP journal layout (Advanced)External ID, date, account, debit, credit, memo, subsidiary, department, class, with amortization linesSnapshot ID and content hash in every row

Exports are generated in your browser. Exports of open periods carry the watermark “Draft, not approved”. Every download from the Exports and Board pack screens is recorded in the audit trail.

R&D time record

R&D is independent of treatment: OpEx work can still qualify as R&D for tax purposes. In every edition a rule or override can set the R&D flag, and the Overview shows R&D hours. R&D categories (for example experimental development, or an IP right for IP Box), the time record and the jurisdiction layouts are in Advanced:

  • Poland: ulga B+R and IP Box (time per IP right)
  • United Kingdom: R&D
  • United States: Section 174 and Section 41 qualified wage summary
  • Canada: SR&ED; Australia: RDTI; Netherlands: WBSO

Each layout regroups the same qualifying hours and wage cost for your advisor to check. CapRadar does not apply a credit or deduction rate and does not decide eligibility.

Amortization

In Advanced, enter the in-service date, useful life in months and capitalized cost of an initiative, and CapRadar builds a straight-line schedule (the last month takes the rounding remainder). The ERP journal layout includes the amortization lines.

Plan and forecast

In Advanced, enter planned CapEx and OpEx per initiative and month on the Plan screen. CapRadar shows actual CapEx against the plan and a year forecast that uses actuals up to the selected month and the plan after it; a missing later plan leaves the forecast empty.

Journal entry files

Map classes to general ledger accounts (debit and credit per class, and the amortization accounts) on the Exports screen; until you save a mapping, default accounts are used. From a locked period, CapRadar generates a balanced journal CSV in your browser, split by the person's cost centre on the period end date. Advanced adds the ERP layout with amortization lines. CapRadar creates files only; it posts nothing to any system.

Non-labour costs

In Advanced, import contractor invoices, software licences, cloud and other costs as a CSV (epic,date,amount,vendor,cost_center). Each cost takes the class of its epic through the same overrides, rules and phases, so the epic must already be classified. Costs are included in totals, snapshots, hashes and exports. Importing a file again replaces the costs of the months in it; locked months are refused. No file attachments are stored.

Inbox and scheduled packs

In Advanced, a finance admin schedules a pack monthly, quarterly or at the start of the fiscal year. A cadence is saved the moment you pick it. On that UTC day a notice arrives in the in-app inbox. The inbox also receives notices when a period is locked, when a period in review gains a late change, and approval requests made through the Rovo agent. Recipients are approver and reviewer role holders and the person who saved the schedule. CapRadar sends no email, Slack or webhook messages.

Roles and permissions

CapRadar roles
RoleCanCannot
Finance admin (Jira administrators and the finance group)Policies, rules, rates, phases, overrides, imports, calendars, prepare and waive checks, approve and lock, reopen, exports, group mappingApprove a period they prepared when separation of duties is on
ApproverApprove and lock, reopen with a reasonEdit rules, rates, phases or overrides
Reviewer (Advanced)Sign the review stepLock, or review a period they prepared
Engineering managerSign off the hours of spaces they can browse (Advanced, separation of duties on); hours-only viewsSee rates or cost; edit rules, phases or overrides
Auditor (Advanced)Read locked periods on Close & sign and run VerifyMake any change
Viewer and other Jira usersHours-only Overview, To classify, space page, work item panel and gadget for spaces they can browseSee cost, rates or per-person cost

Roles are mapped to Jira group names on the admin page (case-insensitive) and computed on the server. Lists are filtered to the spaces the user can browse; finance roles see all spaces. The viewer group is recorded and does not change Jira browse access.

AI suggestions

In Advanced, a Jira administrator can turn on AI suggestions on the Agent screen. They are off by default. For one epic that is already in CapRadar, CapRadar reads the summary (up to 200 characters) and description (up to 1,500 characters) with that administrator's Jira permissions and sends them, with the work type, labels and components, to Forge LLM, a model hosted by Atlassian inside the Atlassian cloud. The answer proposes a class, a phase and an R&D category with a reason. Nothing is stored until a person applies it, which saves an override (and a phase, when one was proposed) with their reason.

Rovo agent guide

The CapRadar agent is part of the Advanced edition. Open Rovo chat in Jira and choose CapRadar. Rovo must be available on your site. The Agent screen in CapRadar lists common workflows, each with an example prompt you can copy into Rovo and a button that opens the related CapRadar screen.

Questions it answers

Period summaries, explanations of a classification, hours per space and epic, initiatives, the unclassified queue, close status and verification, period comparisons and trends, adjustments, data issues (missing rates and hours with no person), the R&D summary and evidence, rule simulation, the audit sample, variance drivers, likely misclassifications, calibration, stored plan lines, journal previews and coverage.

Actions it can take after you confirm

  • Propose a classification, set an epic phase and funding date, create overrides for up to 20 work items with a reason
  • Save a rule as a draft; a draft does not classify anything
  • Prepare a period for review and request approval inside CapRadar
  • Record a non-labour cost line, set a plan line, schedule a pack, queue a draft auditor request for locked periods
  • Save a draft document such as a methodology memo, a variance commentary or an R&D narrative, labelled “draft, AI-assisted, to be reviewed”

Each write first returns a summary and a one-time confirmation token that expires after 10 minutes. These actions change CapRadar data only, never Jira, and most need a finance admin. Approve, lock, reopen and sign stay on Close & sign because they need an explicit attestation.

Rules the agent follows

  • It answers only from CapRadar data and never invents spaces, keys, numbers or rules.
  • It always states whether a period is open, in review, approved or locked, mentions adjustments and names the measurement method.
  • It explains your configured policy and does not give accounting or tax advice.
  • It hides amounts when the caller has no finance role, and never outputs account IDs or email addresses.
  • It says when it does not know.

Skills

  • period-close: Ask it to check whether a month is ready to close, prepare the period for review and request approval.
  • classify-work: Ask why a work item is CapEx, OpEx or R&D, or what is still unclassified.
  • variance-audit: Ask how two periods compare, what looks unusual, or for an audit sample.
  • rd-evidence: Ask for qualifying R&D hours and cost per space and the work items that back an R&D claim.
  • auditor-pack: Ask for a journal preview, an auditor request for a locked period or a scheduled auditor pack.

Approve, lock, reopen and sign stay in the app; every write waits for your confirmation.

Data, privacy and security

  • CapRadar stores its data in Atlassian Forge hosted storage (Forge SQL and the Forge key-value store), following your Jira site's data residency. Classifications are stored only in CapRadar; CapRadar writes nothing to your work items.
  • Stored: account IDs (through an internal person key), worklog metadata (work item, start, duration), work item fields used by rules and allocation, status and assignee intervals, absence dates and type codes, cost centres and team shares, rates you import, non-labour cost lines, plans, text that users type (override and waiver reasons, phase evidence notes, Rovo drafts, vendor references), approvals with the signer's time zone, the Jira group names you map, and audit entries.
  • Not stored: worklog comments, work item summaries and descriptions, comments, attachments, email addresses, display names and space names. To show people and spaces by name, CapRadar reads display names (read:jira-user) and space names (read:jira-work) from Jira when a screen loads, uses them for that response only and does not store them.
  • Hours worked per person can be personal data. If you use per-person reports or allocation, check your works council or employee information duties.
  • When Atlassian reports an account as closed, CapRadar erases or pseudonymises its account ID and keeps a random person key, so signed snapshots stay valid.
  • Data is kept in Forge hosted storage while CapRadar is installed. CapRadar has no automatic deletion schedule, so signed periods stay available as evidence. After uninstall, Atlassian deletes the app's data under its Forge retention rules.
  • AI suggestions (Advanced, off by default) send one epic's summary and description to Forge LLM inside the Atlassian cloud and store nothing. See AI suggestions.
  • No data leaves Atlassian. See Privacy, Security and the DPA.

Editions

CapRadar comes in two editions, licensed through Atlassian Marketplace.

  • Standard: worklog sync with the 24-month backfill, Tempo hours, timesheet-free allocation and the calibration report, rates with the loaded multiplier and blended fallback, rules and the simulator, policy templates with the default policy and its versions, ASU 2025-06 phase fields, overrides, the To classify queue, fiscal and working calendars, organisation dimensions, the period close with a single approver or two-person approval, approve and lock, post-lock adjustments, the CSV pack, the board pack, the generic journal CSV, the R&D flag, English and Polish, and all Jira surfaces.
  • Advanced: everything in Standard, plus imported attribution, absence import, monthly share costing, the coverage check, multiple policies with space assignment, policy diff and standard simulation, the review step with separation of duties on by default and engineering manager sign-off, the Reviewer and Auditor roles, signed snapshots with the SHA-256 content hash and signature rows, the hash chain with Verify, the auditor PDF with sample, XLSX exports, the ERP journal layout, R&D categories and jurisdiction layouts, amortization, team shares, non-labour costs, plan and forecast, scheduled packs, and AI suggestions with Forge LLM.
  • Rovo agent (Advanced): the CapRadar agent in Rovo chat. It is not part of Standard. See Rovo agent guide.

Since version 2.35.0 (26 October 2026), signed snapshots, the hash chain with Verify and the auditor PDF are part of Advanced. They were in Standard before. In CapRadar, Settings, Access, Edition lists all 18 Advanced features.

Languages

The interface is available in English and Polish. CapRadar uses the language of your Jira profile: Polish when your Jira language is Polish, English for every other language. There is no separate language setting in CapRadar. Text stored with a record, such as rule names, stays as it was saved. The signed attestation stays in English, with a Polish rendering shown under it. CSV files keep their English column names, and a Polish pack adds columns-pl.csv with the Polish labels. The auditor PDF is in English. Some labels added in version 2.3.0 are shown in English in the Polish interface until their translation ships.

FAQ

Do we need timesheets?

Totals and the close use Jira worklogs. Where people do not log time, the Allocation screen allocates time from Jira work item data (resolved work items or in-progress days), and where attributed worklogs exist, the calibration report shows how close the allocation is.

We use Tempo. Does CapRadar work?

Yes. CapRadar reports hours and cost per work item, epic and space from the Jira copies of Tempo worklogs. Those copies do not identify the person, so per-person numbers come from allocation or from an imported attribution CSV (Advanced).

Does CapRadar decide what we capitalize?

No. You configure the policy, rules and phases, and you approve each period. CapRadar applies your configuration consistently and records why each hour was classified.

Can a signed period change later?

No. Later changes become post-lock adjustments in the next open period. Reopening requires an approver or finance admin and a reason; the old snapshot is kept and the next lock is chained to it.

Who can see salaries or rates?

Finance roles only. Engineering managers and viewers see hours. The rule is enforced on the server, in reports, in the gadget and in Rovo.

Can we search the class in JQL?

The class is stored in CapRadar only, so it is not available in JQL. Use the work item panel, reports or Rovo.

Does CapRadar post journal entries to our ERP?

No. It generates journal entry files from locked periods for you to import. Posting would need a connection outside Atlassian.

How does CapRadar relate to MarginRadar?

They are separate apps from the same family. MarginRadar tracks cost, burn rate and margin. Separate apps cannot share storage, so rates move over as a CSV file in CapRadar's rate format.

Troubleshooting

Hours are missing from a period
Check the freshness line on the Overview and the sync status on the admin page. Start the backfill if it never ran. Work assigned to a period uses the worklog start time in UTC.
CapRadar says it is read only
The hourly reconcile failed or has not succeeded for six hours. Saves resume after the next successful reconcile; your data is unchanged.
Many hours are unclassified
Open To classify and classify the top epics, or add a rule. The policy default is UNCLASSIFIED on purpose.
The period cannot be locked
A blocking check failed: unclassified hours or missing rates. Fix the item or have a finance admin waive it with a reason.
I cannot approve
Separation of duties is on and you prepared or reviewed this period, a required sign-off or review is missing, or you are not an approver or finance admin.
Cost columns are empty
Cost is shown to finance roles only. Check your group mapping on the admin page.
Verify fails
The file changed after export, or it belongs to a superseded snapshot. Export again from the locked period and compare the snapshot ID.

Still stuck? See Support.

More Radrly apps for Jira