Working Day Guard for Jira

By Rillnook Labs. Marketplace release pending.

Keep due dates aligned with the days your project works.

Choose working weekdays, enter holidays and closure ranges, and add explicit working-date overrides. Preview an unsaved policy, start in OBSERVE, then enable ENFORCE when ready. Eligible non-working dates move to the next or previous working day within your search limit.

Three modes, one project calendar

• OFF stops calendar processing after minimal project resolution.
• OBSERVE records a proposed correction without updating Jira.
• ENFORCE may update the standard Due date after permission, freshness, policy and duplicate checks.

Correction happens after Jira saves an issue and delivers its event. Publishing a policy does not scan existing issues. Events in the 60 seconds following publication are skipped conservatively; make a new explicit Due date change after that guard when correction is wanted. No guaranteed correction time or atomic protection against a simultaneous Jira edit is offered.

The app runs on Atlassian Forge and declares no external runtime egress. It uses no live holiday feed, external application server, LLM or external analytics endpoint. Website delivery and support email are separate processing flows described in the Privacy notice.

Active subscriptions and evaluations enable paid features. Inactive or unavailable licenses make configuration and visible audit read-only. Authorized data-response controls are separate from paid processing. They do not provide unrestricted access to another project's data.

No custom-date-field support, SLA calendar, reminders, bulk repair or pre-save blocking is included. See the guide, support and privacy notice. Pricing will appear on the approved Marketplace listing when published.