Glossary
This glossary explains the FieldCraft and Jira terms you meet in these docs.
Fields and valuesβ
| Term | Meaning |
|---|---|
| Calculated field | A FieldCraft field whose value the app works out from the work item's data. You can't edit it. Every field type except T-Shirt Size is calculated |
| Field type | The kind of FieldCraft field, such as Time Between. In Jira's list of field types, each one starts with FieldCraft: . See Field types |
| Field context | Jira's setting for which spaces and work types a field applies to. Each context has its own FieldCraft configuration |
| Configuration page | The FieldCraft page where you set what a field calculates in one context. See Configure a field |
| Recipe | A ready-made field for one goal, such as Cycle time. New field from recipe creates the field with its settings filled in. See Field recipes |
| Stored value | The value Jira keeps in the field. JQL, boards, dashboards and exports use it |
| Counting value | A value that grows with time, such as the time in the current status. On the work item, you see it up to the current moment. Its hover says Still counting since |
| Display rule | How a number looks on the work item and in lists: a traffic light or a progress bar. Search and exports keep the number. See Show a traffic light or progress bar |
| Status category tokens | Any To Do status, Any In Progress status and Any Done status in a status list. Each one covers every status of that category, including statuses you add to workflows later |
| Customer and team | In comment fields, the customer is the reporter or a portal-only customer. The team is everyone else |
| T-shirt points | The number a T-Shirt Size size stands for. A Rollup field can add them up on the parent |
Calculationβ
| Term | Meaning |
|---|---|
| Background calculation | FieldCraft recalculates values on the server when work items change. The switch is Recalculate when work items change. See How values stay current |
| Update parents and children | The switch that lets a change on one work item update fields on its parent, children or linked work items |
| Hourly refresh | The run that brings counting values up to date in search and lists. Values that have counted longer update less often |
| Reindex | A run that fills in or recalculates values on existing work items that match a JQL query. It's also called recalculation. See Recalculate existing work items |
| Suggested update | An offer on the Calculation tab to fill in a new field, or to update values after you change a configuration or a calendar |
| Hourly calculation budget | The most background work FieldCraft does on your site in one UTC hour: 10,000 Jira API points. See Hourly calculation budget |
| Jira API points | The unit Jira uses to limit how much an app may call it. FieldCraft estimates the points of each request it makes |
| Activity | The tab that lists every hourly refresh and reindex. See Follow runs on the Activity tab |
Work calendarsβ
| Term | Meaning |
|---|---|
| Work calendar | Working hours, breaks, holidays and a time zone. Time-based fields count only the time inside them. See Work calendars |
| Working time | Time inside a calendar's working hours, without its breaks and holidays |
| Working day | The average working day of a calendar. On the 24/7 calendar, a working day is 24 hours |
| 24/7 calendar | A calendar where every hour of every day counts. Fields without a calendar count this way |
Access and permissionsβ
| Term | Meaning |
|---|---|
| App access | Some field types read data with FieldCraft's own access. That can include work items the person viewing the field can't open. These types are the Jira expression types, Rollup and the Parent Field types |
| Acknowledge | A Jira admin confirms that a field may show such data to everyone who can see the work item. Until then, the field doesn't calculate and keeps its last value. See Acknowledge app access |
| Jira admin | A person with the Administer Jira global permission. Jira admins create and configure FieldCraft fields |
| Space admin | A person with the Administer projects permission in a space. Space admins see their space's FieldCraft fields and can recalculate them. See See FieldCraft fields in a space |
AI assistantsβ
| Term | Meaning |
|---|---|
| AI assistant tools | The FieldCraft actions that Rovo, Claude or ChatGPT can use, such as explaining a value. See AI assistant tools |
| Plan | A change that an assistant prepares and shows you before anything happens. The assistant applies it only after you confirm, within 15 minutes |
Jira termsβ
| Term | Meaning |
|---|---|
| Work item | One piece of work in Jira, such as a story, a bug or a request |
| Space | A container of work items with its own settings. Company-managed spaces share settings across the site. Team-managed spaces keep their own |
| Service space | A Jira Service Management space, where customers raise requests on a portal |
| Work type | The kind of work item, such as Story, Bug or Epic |
| Site | Your Jira Cloud site, for example example.atlassian.net |
| Screen | In company-managed spaces, the set of fields a work type shows. A field appears on a work item only when it's on the screen |
| JQL | Jira Query Language, which you use to search work items. See Search and report with FieldCraft fields |
Relatedβ
-
Limits: the numbers that apply to FieldCraft.
-
Known limitations: what FieldCraft doesn't do, and what to do instead.
-
FAQ: short answers to common questions.