The R&D claim is due, the advisor sends a list of questions, and the answers are spread across Jira, a payroll export and the memory of two engineering managers. The hours were logged at the time. The decision about which of them were R&D usually was not.
I'm Marcin, founder of Radrly. We build CapRadar, a software capitalization and R&D time app for Jira Cloud. Below are five questions an R&D advisor typically asks, how you can answer each one from native Jira, and what CapRadar adds. None of this is tax advice: eligibility, rates and what goes into the claim stay with you and your advisor.
1. Which work was R&D, and who decided?
Native. Most teams add a label such as rnd or a select field on the epic and copy it down with an Automation rule. That marks the work item. It does not record why, who decided, or when the decision was made, and an edit to the field later leaves only the field history.
CapRadar. The R&D flag is set by a rule (space, work type, label, component, custom field or a JQL subset) or by an override on a worklog, work item, epic or initiative. An override needs a reason of 10 to 500 characters and can carry a ticket or memo reference, and every override is in the audit trail. The work item panel shows the R&D flag and the decision path.
2. Is R&D the same as capitalized work?
No, and the records should not force it to be. A spike in an OpEx epic can still qualify as R&D, and capitalized build work may not. In CapRadar the R&D flag is independent of the CapEx or OpEx treatment, so one hour can be OpEx and R&D at the same time. The Overview shows R&D hours next to CapEx, OpEx and unclassified hours in every edition.
3. Whose hours, on which dates?
Native. An issue search export gives one row per work item with total time spent, which loses the person and the date of each worklog. Worklog-level data needs the REST API and a script.
CapRadar. It reads every native worklog with its author and date, including a 24-month backfill, and classifies each worklog on its own date. R&D packs (Advanced) show each person by their Jira display name. On Tempo sites the Jira copy of a worklog does not identify the person, so those hours carry the label "no per-person attribution". An imported Tempo report or percentage CSV (Advanced) fills that in as imported attribution, shown in the R&D packs.
4. Were the records changed after the fact?
Native. Jira has no period lock. Anyone with Edit Own Worklogs or Delete Own Worklogs can change last year's worklog today.
CapRadar. Approve and lock closes a period, on Standard too. A worklog added, changed or deleted for a locked month later becomes a post-lock adjustment in the next open period, with its source period, hours and cost, and the locked month stays as it was. Signed snapshots with a SHA-256 content hash and Verify are (Advanced). The hash makes a change detectable; it does not prevent one.
5. Can you give me the hours in the layout my claim uses?
Native. A spreadsheet per claim, rebuilt every year.
CapRadar (Advanced). R&D categories, for example experimental development or an IP right for IP Box, the time record and the jurisdiction layouts:
Country | Layout |
|---|
Poland | ulga B+R, and IP Box with 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. Rates and cost are visible to finance roles only; the space page shows R&D hours with no amounts. The R&D pack CSV is built in your browser from the screen.
What still sits outside Jira
The technical narrative of what was uncertain and what was tried lives in the work items and in your engineers' heads, and a claim needs it in words. The Rovo agent (Advanced) can answer questions such as qualifying hours per space and the work items behind them, and save a draft R&D narrative labelled "draft, AI-assisted, to be reviewed". A person still writes and signs the final text. Payroll stays the source for wages, and CapRadar posts nothing to any system.
Listing: CapRadar on the Atlassian Marketplace.
When your advisor asks which Jira hours were R&D, how long does it take your team to answer?