Skip to main content

FieldCraft FAQ

This page gives you short answers to common questions about FieldCraft. For step-by-step help, follow the links.

Values​

Do values show in JQL, boards, dashboards and exports?​

Yes. FieldCraft stores each value in the Jira field, so you can search, sort and export it without opening the work item.

See Search and report with FieldCraft fields.

Do fields fill in on existing work items by themselves?​

No. FieldCraft calculates a value when a work item changes or someone opens it. To fill in older work items, accept the suggested update on the Calculation tab, or run a reindex.

See Recalculate existing work items.

Do search and the work item always show the same value?​

No. The work item view always shows you the current value. Search updates within seconds of a change, but values that still count update every hour or less often.

See Search, boards or exports show an old value.

Can a field stop updating?​

Yes. Rollup, Parent Field and Jira expression fields wait until a Jira admin acknowledges app access, and keep their last value until then. A failed calculation also keeps the last value.

See A field keeps its last value and doesn't update.

Where do I see values that failed?​

On the Activity tab. For an hourly refresh, select the failed count to see why each value failed.

See Some values failed to calculate.

Does FieldCraft change work item history or send notifications?​

No. FieldCraft writes values without a history entry, and nobody gets a notification. Hover over a value to see when FieldCraft last calculated it.

See How values stay current.

Fields and types​

Which field should I add first?​

A recipe. New field from recipe lists 56 ready-made fields by goal, such as cycle time or reopen count. You can check one on your own work item before you create it.

See Create a field from a recipe.

How many field types are there?​

There are 25. They cover time, status history, field history, comments, parent and linked work items, totals and estimates, and Jira expressions.

See Field types.

Can people edit FieldCraft fields?​

Only T-Shirt Size. FieldCraft calculates every other field type, and you can't edit those.

See T-Shirt Size.

How do I change what a field calculates?​

On its configuration page. On the Fields tab, open the field's β€’β€’β€’ menu, and select Edit configuration.

See Configure a field.

Why can't I see a field on a work item?​

It isn't on the work type's screen, or its context leaves out the space.

See The field doesn't appear on the work item.

How do people know what a field measures?​

From its description. Add one with Edit details in the field's β€’β€’β€’ menu, for example "Working hours from In Progress to Done".

See Fields.

Does FieldCraft work in company-managed and team-managed spaces?​

Yes. In company-managed spaces, you add a field to screens. In team-managed spaces, a space admin adds it in the space's settings.

See The field doesn't appear on the work item.

Can I use FieldCraft with Jira Service Management?​

Yes. The Service and support recipes track time to first response, requests waiting for the team, and the last customer comment. The values show to agents, not on the customer portal.

See Track time to first response on requests.

Do time-based fields count nights and weekends?​

No, not on a work calendar. Only working hours count, without breaks and holidays, in the calendar's time zone. A field without a calendar counts every hour.

See Work calendars.

Can teams with different hours or time zones use FieldCraft?​

Yes. Create a calendar for each team, up to 10 per site, and choose the right one in each field's configuration. Each field context has its own configuration, so one field can use another calendar in another space.

See Create a work calendar.

Calculation and performance​

When does FieldCraft recalculate a value?​

When the work item changes. FieldCraft also checks a value when someone opens the work item, and refreshes values that still count. A parent updates 20 seconds after its children stop changing.

See How values stay current.

Does FieldCraft slow down the work item view?​

No. The view shows the stored value, and FieldCraft calculates again only when the value may be out of date. A calculation that takes over 10 seconds finishes in the background.

See How values stay current.

Is there a limit on how much FieldCraft calculates?​

Yes. Background work uses at most 10,000 Jira API points per site in each UTC hour. Work beyond that waits for the next hour, and opening a work item never waits.

See Hourly calculation budget.

Can I raise the hourly budget?​

No. It's fixed, so one busy site never slows down others. To finish a reindex sooner, give it a narrower scope.

See A reindex says "Waiting for next hour's budget".

How long does a reindex take?​

The Reindex dialog tells you before you start. It estimates the number of work items and the time at the hourly budget.

See Recalculate existing work items.

Can I turn background calculation off?​

Yes. Turn off Recalculate when work items change on the Settings tab. Values then update only when someone opens a work item, or when you reindex.

See FieldCraft settings.

Security and data​

Does data leave Atlassian?​

Yes, but only error reports and usage counts. FieldCraft sends reports of its own errors and usage counts to Sentry in the US. They never contain work item content, field values, JQL or people's names.

A site admin can turn them off. See Turn them off.

Where does FieldCraft keep its data?​

In Jira and on Atlassian Forge. Jira stores the values and the field configurations. Work calendars, settings and calculation records are in FieldCraft's storage on Forge.

See Data security and privacy.

Does FieldCraft read comment text?​

No, not in comment fields. Comment Date, Commenter and Last Comment From read who wrote a comment, when, and whether it's public.

See Comments.

Can a field show data that a viewer can't open?​

Yes, for Jira expression, Rollup and Parent Field types. They read data with FieldCraft's access, and everyone who can see the work item sees the value. That's why a Jira admin acknowledges each one.

See Acknowledge app access.

Who can create and change fields?​

Jira admins. Space admins see their space's fields and can recalculate them. Everyone who can see a work item sees its values.

See Permissions.

Licensing and updates​

What happens when the license ends?​

Nothing recalculates. Work items show FieldCraft app is not licensed in the fields, while search and exports keep the last stored values. Renew the license, then reindex.

See "FieldCraft app is not licensed".

Do updates need an admin?​

Only major versions. Other updates reach your site automatically. A major version waits until a site admin approves it in Connected apps in Atlassian Administration.

See Update from an older version.

Do my fields stay when I update from an older version?​

Yes. Your fields, their settings and their values stay. Parent Field and Jira Expressions - Text fields then wait for a Jira admin's review.

See Update from an older version.

AI assistants​

Which AI assistants work with FieldCraft?​

Rovo, and AI clients that support MCP, such as Claude and ChatGPT.

See Connect Rovo, Claude or ChatGPT.

Do I need a Rovo license for Claude or ChatGPT?​

No. An admin enables the tools for other AI clients in Atlassian Administration.

See Connect Rovo, Claude or ChatGPT.

Can an assistant change my fields?​

Yes, if you're a Jira admin, and only after you confirm. The assistant shows you a plan first, and nothing changes until you confirm it.

See Use FieldCraft with AI assistants.

Can an assistant tell me about work items I can't see?​

No. Each tool checks that you can browse a work item before it answers. A value can still come from data you can't open, as on the work item itself.

See AI assistant tools.

Support​

How do I get help?​

Through our support portal. Copy the diagnostics on the Help & support tab first, and add them to your request.

See Get help from support.