Skip to main content

Known limitations

This page lists what FieldCraft doesn't do today, and what you can do instead.

For the numbers, such as how many calendars you can create, see Limits.

Values on work items​

LimitationWhat you can do instead
Calculated fields show only on the work item view. They don't appear on create or transition screens, in bulk edit, or on the customer portal. T-Shirt Size is the one field people edit, and it appears on all of them.Read the values on the work item, in lists and with JQL. See The field doesn't appear on the work item.
Values are written without a history entry, and without notifications. The work item's history doesn't show earlier values.Hover over a value to see when FieldCraft last calculated it, and why.
FieldCraft fields keep no change history of their own. Field history types can't track another FieldCraft field.Track the field it reads instead, for example Status. See Field history.

Updates​

LimitationWhat you can do instead
Watcher and vote counts update only when someone opens the work item, or when you reindex. Jira sends no event when they change.Open the work item, or recalculate existing work items.
Changes on a parent work item reach its children only in Parent Field types. A Jira expression that reads the parent updates when its own work item changes or is opened.Use Parent Field, Parent Field - User, Parent Field - Date or Parent Field - Number. See Parent and linked work items.
Jira expressions aren't refreshed every hour, even when they read the current time.For the time left until a date, use Countdown.
A Rollup of values that still count, such as Time in Status, moves only when a child changes or the parent is opened.Reindex the parents when you need current totals in search.
Older values that still count update less often in search. After 7 days, the hourly refresh updates them every 6 hours. After 30 days, once a day.Open the work item. Its view always shows the current value.
Rollup and Parent Field types follow other work items only while Update parents and children is on.Keep the switch on. See FieldCraft settings.
Fields that read data with the app's access don't calculate until a Jira admin acknowledges them. Until then, they keep their last value.See Acknowledge app access.

Field types​

LimitationWhat you can do instead
Comment Date, Commenter and Last Comment From read the first 1,000 comments of a work item. On longer threads, they can miss the newest comments.Check the newest comments on the work item itself. See Comments.
Rollup counts a day of time tracking as 8 hours, not as the working day of a work calendar.Store the value in Hours. See Rollup.
Rollup reads one level of children, and it can't read another Rollup field.Create a Rollup field for each level, each reading a field the children hold themselves.
Parent Field lists every linked value, repeats included, for example Done, Done.To count open blockers, use the Open blockers recipe.
Previous Value stores text, such as a person's display name. A renamed person or option keeps the old name.Search by the name the value had at the time of the change. See Previous Value.
T-Shirt Size searches the slot, not the label. With the Fibonacci 1–21 preset, the size labeled 5 is in the slot M.Search the points with "Field name.Points". See T-Shirt Size.

Work calendars​

LimitationWhat you can do instead
A working day can't cross midnight.For a night shift, use 00:00 to 00:00 with a break from the shift's end to its start. See Create a work calendar.
Calendars from the Create work calendar menu start in Central European Time.Change the Time zone after you create the calendar.
You can't delete a calendar while a field uses it.Choose another calendar for those fields first.
A field restored from the trash can point to a calendar you deleted. Time in Status then counts every hour of every day. Time Between and Countdown fail until the field has a calendar.Choose another calendar in the field's configuration.

Fields and administration​

LimitationWhat you can do instead
FieldCraft can't restore a field from the trash. Jira keeps it for 60 days.Restore it in Jira's Deleted fields. See Move a field to the trash.
Only Jira admins create and configure fields, and acknowledge app access. Space admins can see their space's fields and recalculate them.Ask a Jira admin. See See FieldCraft fields in a space.
A field from a recipe gets a context for all spaces and work types.Limit the context in Jira afterwards. See Configure a field.
The recipe's screen list leaves out team-managed spaces. They choose their fields in each space's own settings.Add the field in the team-managed space's settings.
The hourly budget is fixed. You can't raise it.Give a reindex a narrower scope. See Hourly calculation budget.

AI assistants​

LimitationWhat you can do instead
A field that an assistant creates gets a context for all spaces and work types.Limit the context in Jira afterwards.
When the hourly budget is used up, previews and recalculations stop with a message. The assistant doesn't try again on its own.Ask again after the start of the next hour. See AI assistant tools.

Products​

LimitationWhat you can do instead
FieldCraft is for Jira Cloud only. It isn't available for Jira Data Center.Use FieldCraft on a Jira Cloud site.
  • Limits: the numbers, with what to do when you reach one.

  • Troubleshooting: fixes for specific problems.

  • FAQ: short answers to common questions.