Calculate due dates excluding holidays
The most common reason people install this app: "every new support work item gets a due date five working days out, and it must not land on a public holiday."
What Jira does on its own
{{now.plusBusinessDays(5)}} is free, built in, and skips Saturday and Sunday. If
your team works Monday to Friday and public holidays genuinely do not matter to your
commitments, use it and stop reading — you do not need this app.
It has one gap: it does not know your holidays. On 22 December it will happily promise 29 December to a customer whose ticket nobody will look at until January. AUTO-971 is the open request to fix that.
The rule
Trigger: Work item created
Action: Calculate Working Date
| Field | Value |
|---|---|
| Working calendar | Norway Support |
| Start date | {{now.jiraDate}} |
| Working days to add | 5 |
| If the start date is not a working day | Move it to the next working day |
Action: Edit work item → Due date → the smart value this action produced.
The rule builder offers that smart value in its autocomplete once the action is in the rule. Pick it from the list rather than typing it — Jira builds the name, not this app.
What that produces
With a Monday–Friday calendar holding 24, 25 and 26 December:
| Created on | Due date | Why |
|---|---|---|
| Mon 21 Dec | Thu 31 Dec | Skips the three holidays and the weekend |
| Wed 23 Dec | Tue 5 Jan | Only 4 working days remain in December |
| Sat 26 Dec | Fri 8 Jan | Start rolls to Mon 28 Dec first, then counts five |
That last row is the adjustment setting doing its job. Without it, counting starts on a Saturday and the answer is a day earlier.
Only working days should get a due date
Add a Check Working Day action and a condition before the calculation, so nothing is promised on a day nobody is working.
When the trigger is not "now"
Any date field works as the start:
{{issue.created.jiraDate}}— five working days from creation, not from when the rule happened to run.{{issue.duedate}}— extend an existing deadline by three working days.{{issue.fields.customfield_10050}}— count from your own date field.
The value must arrive as year-month-day. If a smart value gives you a full timestamp
instead, add .jiraDate to it.
If you type dates in yourself rather than mapping a field — 17/03/2026 instead of
2026-03-17 — set Date format on the action to match how you write them. The app
will not guess between day-first and month-first, because 03/04/2026 is two
different days and picking the wrong one would set a deadline a month out without
anyone noticing. Year-month-day is understood whichever option you choose.
If it fails
The rule stops and the owner gets an email with the reason. This app will never write a date it is not sure about — a wrong due date is worse than no due date, because nobody notices a wrong one.
See Troubleshooting.