How it works
Which calendar applies
Fields, the panel and automation steps use the calendar of the work item’s project, or the default calendar. JQL functions and automation steps can name a calendar instead. Names are not case-sensitive.
What counts as a business day
For each date, Daywise checks in this order:
- An extra working day is always a business day.
- A short day is a business day with its own hours.
- A closure is not a business day.
- A holiday of the chosen types is not a business day, unless you unticked it. Some holidays start during the day, for example New Year’s Eve from 14:00 in Norway. Then the day ends when the holiday starts.
- Otherwise the work week decides.
Dates are local to the calendar’s time zone.
Counting business days
Counting from a start date to an end date counts the business days after the start, up to and including the end. Monday to Wednesday is 2 business days. When the end is earlier, the count is negative. The same day is 0.
Adding business days works like WORKDAY in spreadsheets: the start date itself is not counted. Adding 0 days returns the date if it is a business day, otherwise the next one.
Business hours
Hours count only time inside working hours, on business days, in the calendar’s time zone. Daylight saving changes are handled: a working day is always its local hours long. A date without a time counts from the start of that day’s working hours.
JQL functions
businessDaysFromNow(n)andbusinessDaysFromNow(n, "Calendar"): the date n business days from today.businessDaysAgo(n)andbusinessDaysAgo(n, "Calendar"): the date n business days before today.
Use them with date fields and the operators =,
!=, <, <=,
> and >=. “Today” is the date in the
calendar’s time zone. Jira keeps the result of each query, and Daywise
updates it every hour and whenever you change a calendar.
Fields
- Business days open: business days from creation to resolution, or to today while the work item is open.
- Business days to due date: business days from today to the due date. Negative when overdue, 0 on the due date, empty when there is no due date or the work item is resolved.
Values update when a work item is viewed, when its due date, resolution or project changes, when you change calendars, and once a day for open work items and those resolved in the last three days. On the Fields tab you can switch the daily refresh off, set how many work items it may update per day, and start a refresh.
In team-managed projects, add the fields to the work type first.
Automation steps and their results
| Step | Results |
|---|---|
| Daywise: add business days or hours | {{fetchedDaywiseResult.date}},
{{fetchedDaywiseResult.dateTime}},
{{fetchedDaywiseResult.calendar}} |
| Daywise: count business days or hours | {{fetchedDaywiseCount.value}},
{{fetchedDaywiseCount.calendar}} |
| Daywise: check a business day | {{fetchedDaywiseDay.isBusinessDay}},
{{fetchedDaywiseDay.date}},
{{fetchedDaywiseDay.next}},
{{fetchedDaywiseDay.previous}},
{{fetchedDaywiseDay.reason}},
{{fetchedDaywiseDay.calendar}} |
Dates and times can be smart values such as
{{issue.created}}, {{issue.duedate}} or
{{now}}. Units are days, hours or minutes.
Holiday data
Public holiday data comes from the open-source date-holidays project, available under CC BY-SA 3.0 (data) and ISC (code), with contributors’ attribution in that project. Holiday rules can change; check the preview each year and add closures or untick holidays where your team differs.