Skip to main content

πŸ“‚ FieldCraft

FieldCraft logoFieldCraft adds calculated fields to Jira: cycle time, time in status, reopen counts, first response, story points on the epic, days until due and more. Values are calculated from each work item's history, kept current on the server, and stored in the field, so you can search, sort and report on them.

Get started: create your first calculated field from a recipe and see its value in about 10 minutes.

The FieldCraft admin page on the Fields tab, filtered to three fields, each with its type, ID, screens and contexts

Why teams use it​

  • Numbers Jira doesn't keep. 25 field types read a work item's history, comments, children and parents.

  • Values you can search. JQL, filters, boards, dashboards and exports use the stored value. Nobody has to open the work item first.

  • Working time, not clock time. Work calendars leave out nights, weekends, breaks and holidays, in the time zone you choose.

  • Start from a recipe. Pick one of 56 ready-made fields and check its value on your own work item first.

  • No noise in history. FieldCraft writes values without adding history entries or sending notifications.

  • Clear when something needs you. The Calculation tab shows what waits for you. Hover over any value to see how it was calculated.

  • Ask in plain words. Rovo, Claude or ChatGPT can explain a value or plan a new field.

Who it's for​

  • Jira admins add the fields, set up work calendars and decide how values stay current.

  • Engineering managers and scrum masters follow cycle time, rework and work carried over between sprints.

  • Project and program managers track progress on epics and the days left until due dates.

  • Service desk managers see time to first response and which requests wait for a reply.

  • QA leads count reopens and work sent back from review.

  • Space admins see which FieldCraft fields work in their space and bring the values up to date.

What you can calculate​

QuestionField types
How long did it take, or how long is left?Time in Status, Time Between, Countdown
How often did the status change, and when or by whom?Transition Count, Status Entered Time, Status Entered By
When and how often did a field change, and what was it before?First/Last Field Change Time, Field Change Count, Modified By, Previous Value
Who commented, and who waits for a reply?Comment Date, Commenter, Last Comment From
What does the parent, the epic or a linked work item say?Parent Field, Parent Field - User, - Date and - Number
What do the children add up to? How many links, sprints or comments? How big is it?Rollup, Calculated Metrics, T-Shirt Size
Anything else Jira can compute from the work itemJira Expressions - Text, Number, Date, Date & time and User

Documentation​

SectionWhat you'll find
Get startedInstall FieldCraft, create a field from a recipe and find it in search
Use casesCycle time, first response, story points on epics, reopened work and work due soon
Field recipesAll 56 ready-made fields, with what each one measures and a JQL example
FieldsCreate, configure, check, display, search and trash fields
Field typesEvery field type, its settings, examples and limits
How values stay currentBackground calculation, the hourly refresh, recalculating older work items and the Activity tab
Work calendarsWorking hours, breaks, holidays and time zones for time-based fields
See FieldCraft fields in a spaceThe FieldCraft page in space settings, for space admins
AI assistantsAsk Rovo, Claude or ChatGPT about your fields and values
AdministrationSettings, permissions, licensing and updating from an older version
ReferenceLimits, known limitations and a glossary
Troubleshooting and FAQFixes for common problems, short answers and how to reach support
Data security and privacyWhat FieldCraft stores, what leaves Jira and which permissions it asks for

What's new​

  • Q4 2026: values that stay current on the server, 56 field recipes, 17 new field types, traffic lights and progress bars, and AI assistants. Details

  • All changes

Get help​