Changelog — Step-Free Scheduler for Jira

Written for the person who installed the app, not for a developer. Marketplace release notes are read by buyers.

1.0.0 — first Marketplace submission, not yet released

Deployed to the production environment on 14 September 2026 and waiting on the partner account. Everything below is in that build.

What it does

• Recurring issues from a template — daily, weekly on chosen days, monthly on a date or on "the last Friday", every N of any of those. Jira still has none of its own (JRACLOUD-5185, open since 2005).
• Scheduled reminders — a comment on every issue a filter matches, with a per-run limit so a filter that quietly grows fails visibly instead of commenting on hundreds.
• Digests — one issue summarising what a filter matched, however many matched.
• Business calendars — skip weekends, skip your own holiday list, or move to the next or previous working day.
• The next five runs, shown before you save, worked out by the same engine that runs them. It is where you find out that "the 31st" skips February.
• Run now, so you never wait a week to learn whether a weekly job works.

Daylight saving, which is the part that usually breaks

A schedule is a local time in a named timezone, and the instant is worked out from the calendar every single run — never by adding twenty-four hours to the last one, which is the mistake that turns a 09:00 job into an 08:00 job for half the year. When the clocks go forward and your time does not exist, the job runs at the first minute that does, or skips the day if you prefer. When they go back and it happens twice, it runs once. Both are marked in the run history.

Known limits, stated rather than left to be discovered

• Jobs are dispatched hourly. A job set for 09:00 runs during the 09:00 hour. That is the finest interval the Forge platform offers and we cannot tighten it.
• A job works inside one project. Atlassian gives an app no way to re-check your permissions while a scheduled job runs, and confining each job to the project you proved access to is what we do instead of asking you to make this app a Jira administrator.
• The steps-avoided figure is an estimate, and the screen says so next to it. No API exposes your Atlassian usage meter to an app. There is no money figure anywhere, because Atlassian has not published the overage price.

Fixed before first release — found by running the app against real Jira rather than against its own tests, on 13 September:

• The per-run owner permission check could not exist: Jira refuses another user's account id from anything but an administrator or a Connect app. Every scheduled run would have failed. Replaced with the one-project scope above.
• Digests reported the page size as the match size — "2 issues matched" when four had — because Jira's newer search endpoint returns no total at all.
• Editing a job loaded only its name and schedule but saved the whole action, silently blanking what the job did.
• Two of the three job kinds had no interface, so features the listing described could not be created.
• One failing Jira call ended the whole hourly sweep instead of that one job.
• A new job's first run was bounded by a window ending now, so a late dispatch dropped it silently. It is now owed what fell after it was created.

Where this comes from

This page is rendered from the app's own CHANGELOG.md, which is also what goes into the Marketplace release notes. There is one copy, so the two cannot disagree.

Documentation · Support