Changelog

Anything that changes the result of a calculation is called out explicitly. A date calculator that quietly changes its answers is not one you can build a process on.

1.0.0 — not yet released

First release. Pending Marketplace approval.

Three automation actions

• Calculate Working Date — add or subtract working days using your own working week and holidays
• Check Working Day — is this a working day, and when is the next one
• Count Working Days — how many working days lie between two dates

Working calendars

• Any working week, including Sunday–Thursday and Monday–Saturday
• Non-working dates typed or pasted as a list
• IANA time zone per calendar
• Up to 50 calendars, up to 2,000 non-working dates each

Behaviour worth knowing

• The start date counts as day 0. One working day from a Monday is the Tuesday.
• Working days (movement, start excluded) and working days inclusive (range, both ends counted) are returned separately, because they answer different questions.
• Dates are read exactly as written. A time zone offset on an input never shifts the day.
• An unclear input stops the rule with a specific message rather than producing a date that might be wrong.
• An empty start date is an error, not "today". Use {{now.jiraDate}} for today — assuming today would quietly set the wrong deadline when a mapped field is empty.

A Jira limitation you should know about

• Jira's automation date parser silently rewrites the century on dates more than about 19 years ahead — a due date of 2046 is stored as 1946, with no error and a green audit log. Measured directly against Jira Cloud rather than inferred.
• Working Days refuses to produce such a date rather than let it through, and stops the rule with a clear message (WD-208). The limit moves forward one year every year.

Not included in 1.0

• ICS calendar import
• Automatic public holiday feeds
• Working hours or partial days