Field recipes
This page lists every recipe in FieldCraft's gallery, what it measures and how you search with it.
A recipe is a ready-made field: a field type with its settings already chosen. You pick it in the gallery, check it on one of your work items, and create it. See Create a field from a recipe.
You can change every setting after you create the field.
How to read an entryβ
Field type links to the page of the type the recipe uses.
Needs lists what your site must have:
-
A work calendar: only working hours count. The recipe form offers to create an 8/5 calendar if you have none. See Work calendars.
-
Jira Service Management: the recipe is made for requests in a service space.
-
App access acknowledgement: the field reads other work items. See Acknowledge app access.
-
A story points field, the Sprint field or the Blocks link type: the recipe reads it. The form tells you when your site doesn't have it.
The JQL example uses the recipe's name. If you rename the field, use your name instead.
Rework and flowβ
Reopen countβ
Counts how often a work item came back to a To Do or In Progress status after it was done. You use it to find work that keeps coming back.
Field type: Transition Count
"Reopen count" > 1 ORDER BY "Reopen count" DESC
Times sent back to In Progressβ
Counts how often work went from review or testing back to In Progress. The form picks your review statuses by name, and you can change them.
Field type: Transition Count
"Times sent back to In Progress" > 0 ORDER BY "Times sent back to In Progress" DESC
Times blockedβ
Counts how often work moved to a Blocked or On hold status.
Field type: Transition Count
"Times blocked" > 0 ORDER BY "Times blocked" DESC
Status changesβ
Counts every status change on the work item. You can spot work that moves back and forth a lot.
Field type: Transition Count
"Status changes" > 5 ORDER BY "Status changes" DESC
Time spentβ
Time in Status recipes store working seconds. To find more than 8 working hours, compare with 28800.
Cycle timeβ
Working days from the first In Progress status to the last Done status. The field stays empty until the work item is done.
Field type: Time Between Β· Needs: a work calendar
"Cycle time" > 5 ORDER BY "Cycle time" DESC
Lead timeβ
Working days from creating a work item to its last Done status. You see the whole wait, including time before work started.
Field type: Time Between Β· Needs: a work calendar
"Lead time" > 10 ORDER BY "Lead time" DESC
Time to resolutionβ
Working days from creating a work item to its Resolved date. It stays empty until the work item is resolved.
Field type: Time Between Β· Needs: a work calendar
"Time to resolution" > 3 ORDER BY "Time to resolution" DESC
Time in progressβ
Working time spent in any In Progress status, over every visit.
Field type: Time in Status Β· Needs: a work calendar
"Time in progress" > 0 ORDER BY "Time in progress" DESC
Time in reviewβ
Working time spent waiting in review or QA. You find where work waits for reviewers.
Field type: Time in Status Β· Needs: a work calendar
"Time in review" > 0 ORDER BY "Time in review" DESC
Time blockedβ
Working time lost in Blocked or On hold statuses.
Field type: Time in Status Β· Needs: a work calendar
"Time blocked" > 0 ORDER BY "Time blocked" DESC
Time waiting for customerβ
Working time a request waited for the customer to reply. You can tell your team's time apart from the customer's.
Field type: Time in Status Β· Needs: a work calendar, Jira Service Management
"Time waiting for customer" > 0 ORDER BY "Time waiting for customer" DESC
Time in current statusβ
How long the work item has been in its current status, in 24-hour days. You find work that has stopped moving.
Field type: Time Between
"Time in current status" > 14 AND statusCategory != Done ORDER BY "Time in current status" DESC
Days until dueβ
Working days left until the due date, negative once it's overdue. When the work item is done, it keeps how early or late it finished.
Field type: Countdown Β· Needs: a work calendar
"Days until due" < 0 AND statusCategory != Done ORDER BY "Days until due" ASC
Time left in sprintβ
Working days left until the work item's sprint ends. It's empty outside a sprint and once the work item is done.
Field type: Countdown Β· Needs: a work calendar, the Sprint field
sprint in openSprints() AND "Time left in sprint" < 1 AND statusCategory != Done
Days to releaseβ
Working days left until the release date of the work item's fix version, negative once it has passed.
Field type: Countdown Β· Needs: a work calendar
"Days to release" < 5 AND statusCategory != Done ORDER BY "Days to release" ASC
Dates and peopleβ
Latest sub-task due dateβ
The last due date among the work item's sub-tasks, searchable as a date. It's empty when no sub-task has a due date.
Field type: Jira Expressions - Date Β· Needs: app access acknowledgement
"Latest sub-task due date" <= endOfWeek() AND statusCategory != Done
Last status changeβ
The date and time the status last changed. You find open work that hasn't moved for a while.
Field type: First/Last Field Change Time
"Last status change" < -14d AND statusCategory != Done
First assignedβ
When someone was first assigned to the work item.
Field type: First/Last Field Change Time
"First assigned" >= startOfWeek()
Last updated byβ
The person who made the most recent change to the work item.
Field type: Modified By
"Last updated by" = currentUser()
Status last changed byβ
The person who moved the work item to its current status.
Field type: Modified By
"Status last changed by" = currentUser()
Date startedβ
When work first moved to an In Progress status. The date stays when the work item moves on.
Field type: Status Entered Time
"Date started" >= startOfMonth()
Date doneβ
When the work item was finished. It's empty again if the work item is reopened.
Field type: Status Entered Time
"Date done" >= startOfWeek()
Moved to Done byβ
The person who finished the work item. It's empty again if the work item is reopened.
Field type: Status Entered By
"Moved to Done by" = currentUser()
Previous assigneeβ
The person who had the work item before the current assignee. The value is the person's name as text, so you search it by name.
Field type: Previous Value
"Previous assignee" = "Alice Smith"
Previous statusβ
The status the work item was in before its current status.
Field type: Previous Value
"Previous status" = "In Review"
Last commenterβ
The person who wrote the latest public comment, searchable as a person. You find your work items where someone else wrote last.
Field type: Commenter
"Last commenter" != currentUser() AND assignee = currentUser()
Countsβ
Due date changesβ
How many times the due date moved after it was first set. You find plans that keep slipping.
Field type: Field Change Count
"Due date changes" > 1 ORDER BY "Due date changes" DESC
Comment countβ
The number of comments on the work item, ready to sort and filter.
Field type: Calculated Metrics
"Comment count" > 0 ORDER BY "Comment count" DESC
Linked work itemsβ
The number of work items linked to this one, of any link type.
Field type: Calculated Metrics
"Linked work items" > 0 ORDER BY "Linked work items" DESC
Sub-task countβ
The number of sub-tasks under the work item.
Field type: Calculated Metrics
"Sub-task count" > 0 ORDER BY "Sub-task count" DESC
Watcher countβ
How many people watch the work item. Search catches up when someone opens the work item, or when you reindex.
Field type: Calculated Metrics
"Watcher count" > 0 ORDER BY "Watcher count" DESC
Attachment countβ
The number of files attached to the work item.
Field type: Calculated Metrics
"Attachment count" > 0 ORDER BY "Attachment count" DESC
Open blockersβ
The number of work items that block this one and aren't done yet.
Field type: Calculated Metrics Β· Needs: the Blocks link type
"Open blockers" > 0 AND statusCategory != Done ORDER BY "Open blockers" DESC
Sprint countβ
How many sprints the work item has been in. More than one means you carried it over.
Field type: Calculated Metrics Β· Needs: the Sprint field
"Sprint count" > 2 ORDER BY "Sprint count" DESC
Vote countβ
The number of votes on the work item, for ideas and requests. Search catches up when someone opens the work item, or when you reindex.
Field type: Calculated Metrics
"Vote count" > 0 ORDER BY "Vote count" DESC
Commenter countβ
How many different people commented on the work item.
Field type: Calculated Metrics
"Commenter count" > 0 ORDER BY "Commenter count" DESC
Rollupsβ
These recipes add up values from a work item's children, such as the stories of an epic.
Story points on the epicβ
The total story points of the work item's children, ready for JQL.
Field type: Rollup Β· Needs: a story points field, app access acknowledgement
"Story points on the epic" > 20
Completed story pointsβ
The story points of the children in a Done status.
Field type: Rollup Β· Needs: a story points field, app access acknowledgement
"Completed story points" > 0 ORDER BY "Completed story points" DESC
Epic size in T-shirt pointsβ
Adds up the children's T-shirt sizes as points. Create a field from the T-shirt estimate recipe first.
Field type: Rollup Β· Needs: a FieldCraft T-Shirt Size field, app access acknowledgement
"Epic size in T-shirt points" > 20
% doneβ
The share of the children in a Done status, with a progress bar.
Field type: Rollup Β· Needs: app access acknowledgement
"% done" < 50 AND statusCategory != Done
% of points doneβ
The share of the children's story points that are done, with a progress bar. Large stories weigh more than small ones.
Field type: Rollup Β· Needs: a story points field, app access acknowledgement
"% of points done" < 50 AND statusCategory != Done
Open sub-tasksβ
The number of sub-tasks that aren't done yet. You find work whose sub-tasks are all done while it's still open.
Field type: Rollup Β· Needs: app access acknowledgement
"Open sub-tasks" = 0 AND statusCategory != Done
Remaining time on childrenβ
The total remaining estimate of the children, in hours.
Field type: Rollup Β· Needs: app access acknowledgement
"Remaining time on children" > 40
Parent and moreβ
Parent statusβ
The status of the parent work item, such as the epic, shown on every child. You find open children of a finished parent.
Field type: Parent Field Β· Needs: app access acknowledgement
"Parent status" = "Done" AND statusCategory != Done
Parent priorityβ
The priority of the parent work item, shown on every child.
Field type: Parent Field Β· Needs: app access acknowledgement
"Parent priority" = "High"
Epic ownerβ
The assignee of the epic, on every story and sub-task below it. You search it as a person.
Field type: Parent Field - User Β· Needs: app access acknowledgement
"Epic owner" = currentUser() AND statusCategory != Done
Epic due dateβ
The due date of the epic, on every story and sub-task below it. You can plan and sort by it.
Field type: Parent Field - Date Β· Needs: app access acknowledgement
"Epic due date" <= endOfMonth() ORDER BY "Epic due date" ASC
Blocker statusβ
The status of each work item that blocks this one.
Field type: Parent Field Β· Needs: the Blocks link type, app access acknowledgement
"Blocker status" IS NOT EMPTY AND statusCategory != Done
Sub-task progressβ
Done sub-tasks out of all sub-tasks, like 3/5 done. It's empty without sub-tasks.
Field type: Jira Expressions - Text Β· Needs: app access acknowledgement
"Sub-task progress" IS NOT EMPTY AND statusCategory != Done
T-shirt estimateβ
A size from XS to XL that people pick on the work item, worth 1, 2, 3, 5 or 8 points. An epic can add up the points with a Rollup.
Field type: T-Shirt Size
"T-shirt estimate.Points" >= 5
Service and supportβ
These recipes count a reporter or portal-only customer as the customer, and everyone else as the team.
Last comment fromβ
Customer or Team: who wrote the last public comment. You find requests that wait for your reply.
Field type: Last Comment From Β· Needs: Jira Service Management
"Last comment from" = Customer AND statusCategory != Done
Waiting for the teamβ
Working hours since the customer's last comment, while the team hasn't replied. It's empty once the team replies.
Field type: Time Between Β· Needs: a work calendar, Jira Service Management
"Waiting for the team" > 4 ORDER BY "Waiting for the team" DESC
Time to first responseβ
Working hours from creating the request to the team's first public reply. Until the reply, it counts up to now.
Field type: Time Between Β· Needs: a work calendar, Jira Service Management
"Time to first response" > 4 ORDER BY "Time to first response" DESC
Last customer commentβ
When the customer last commented on the request.
Field type: Comment Date Β· Needs: Jira Service Management
"Last customer comment" <= -2d AND statusCategory != Done
Last team replyβ
When the team last replied publicly on the request. You find requests nobody has answered for a few days.
Field type: Comment Date Β· Needs: Jira Service Management
"Last team reply" <= -3d AND statusCategory != Done
First responderβ
The person on the team who replied publicly first.
Field type: Commenter Β· Needs: Jira Service Management
"First responder" = currentUser()
Relatedβ
-
Create a field from a recipe: pick a recipe and check it before you create it.
-
Search and report with FieldCraft fields: JQL per value type and units.
-
Field types: build a field yourself when no recipe fits.