Work calendars
A work calendar sets the working time that FieldCraft's time-based fields count: working hours for each day, breaks, holidays and a time zone.
With a calendar, a cycle time leaves out nights, weekends and public holidays, so you compare work in working time.
What counts as working timeβ
You set working hours for each day of the week, Monday to Sunday:
-
A day with working hours counts from its start to its end, minus its breaks.
-
A day without working hours is a day off.
-
00:00 to 00:00 is the whole day. An end of 00:00 means midnight.
-
Breaks never count, for example a lunch break from 12:00 to 13:00.
-
A holiday is a whole day off, whatever its usual working hours.
A night shift can't end before it starts on the same day. Use 00:00 to 00:00 with a break from the shift's end to its start.
Time zoneβ
Each calendar has one time zone. Working hours, breaks and holidays apply in that zone, wherever the people who work on the work item are.
Changes to daylight saving time don't move working hours. A 09:00 to 17:00 day stays 8 hours.
For teams in different time zones, create a calendar for each team.
Templates and the defaultβ
You can start from two templates:
-
24/7, Mon-Sun, 00:00 - 00:00 counts every hour of every day.
-
8/5, Mon-Fri, 09:00 - 17:00 counts office hours on weekdays.
The templates use the time zone +01:00 Central European Time - Berlin, Hamburg, Munich, KΓΆln. Edit the calendar to change it.
A field without a calendar counts on a 24/7 calendar.
Your site can have up to 10 work calendars.
Which fields use a calendarβ
You pick a calendar in the configuration of these field types:
Their working day is the calendar's average working day. On an 8/5 calendar it's 8 hours. On a 24/7 calendar it's 24 hours.
A Rollup of time tracking doesn't use a calendar. Its day is 8 hours, unless an AI assistant set another day length.
Example: counting working timeβ
Your calendar Office hours runs Monday to Friday, 09:00 to 17:00, with a break from 12:00 to 13:00. That's 7 working hours a day.
Its time zone is Berlin, and it has a holiday on 2026-12-25.
A work item enters In Progress on Thursday, 24 December 2026 at 15:00. It reaches Done on Tuesday, 29 December 2026 at 11:00.
| Day | Counted |
|---|---|
| Thursday, 24 December | 2 hours, from 15:00 to 17:00 |
| Friday, 25 December | Nothing: a holiday |
| Saturday, 26 and Sunday, 27 December | Nothing: no working hours |
| Monday, 28 December | 7 hours: 09:00 to 12:00 and 13:00 to 17:00 |
| Tuesday, 29 December | 2 hours, from 09:00 to 11:00 |
A Time Between field from In Progress to Done shows 1d 4h: 11 working hours, with a 7-hour working day.
On a 24/7 calendar, the same work item shows 4d 20h.
Change a calendarβ
When you save a change to the working hours, breaks, holidays or time zone, you see Work calendar saved.
Values that FieldCraft already stored still use the old working time.
The Calculation tab then suggests an update for the fields that use the calendar, titled Update values on and the calendar's name. See Recalculate existing work items.
Renaming a calendar changes no value, so you get no offer.
Delete a calendarβ
You can't delete a calendar that a field uses. FieldCraft shows This work calendar is in use and lists the fields.
Choose another calendar for those fields first, then delete this one.
Deleting a calendar can't be undone. If a field in Jira's trash uses it, choose another calendar for that field when you restore it. When Jira's trash holds too many fields to check them all, the dialog says so and still lets you delete; check the calendar of any FieldCraft field you restore later.
Only Jira admins create, change and delete work calendars.
Relatedβ
-
Create a work calendar: set up working hours, breaks and holidays.
-
A duration looks too long or too short: check hours, holidays and the time zone.
-
Measure cycle time in working hours: a complete setup with a calendar.
-
FieldCraft settings: where the calendars live on the Settings tab.