Datum

Apps → Cadence

A Datum app for Jirav2.0.2

Cadence

Recurring Jira issues that fire on time — daily, weekly, monthly or cron, each in its own DST-correct timezone, with a run history you can trust. Never touches your metered automation allowance.

Get it on the Atlassian Marketplace → All apps
ScheduleCadence · Mon 09:00
Repeats Every Monday, 09:00 Active
Template Release checklist 12 tasks
Last run Created SPT-311 Done
Recurring work created on time, from a full template.

The problem

Recurring work — sprint ceremonies, release checklists, weekly maintenance, standing reports — is created by hand or forgotten. Native Jira scheduling is rigid, and a missing run quietly breaks the process that depended on it.

How it works

1

Define the cadence

Create a schedule: daily, weekly, or monthly — with cron rules, business-day awareness and Nth-weekday options on Standard.

2

Templates keep it real

Generated issues come from a template, so each run carries the right fields, sub-tasks and structure — not a blank issue.

3

It runs, and you know it

Each run is recorded; on Standard, failures alert you instead of silently dropping the ceremony.

A Datum app

the promise

Like every Datum app, Cadence is Forge-native and runs inside your own Jira site — free for up to 10 users, with a single honest paid plan after. No separate sign-up, no data leaving your tenant. Why Datum →

Screenshots

Click any shot to view it full size.

FAQ

What's free?

Up to 5 active schedules with single-issue recurring (daily/weekly/monthly) and field pre-fill on generated issues.

Can it make full hierarchies?

Standard recurs whole templates — epic → story → sub-task — not just single issues, with per-schedule overrides.

Does it know about business days?

Yes — Standard's advanced cadence understands cron rules, business days, Nth weekdays and end conditions.

Works well with

Prefab Structured Jira issue templates — pre-fill fields on the native Create screen and scaffold whole epic → story → sub-task trees in one click. Trailkeeper The field-change history and audit trail Jira's native activity view leaves out — who, what, when, from → to. Linger See how long issues sit in each status — time-in-status, cycle time and where work gets stuck.

Explore all Datum apps →

Guides

Best Jira recurring issue apps (2026) The best apps for recurring Jira issues in 2026, compared — scheduling accuracy, automation cost, and which fits a small team or a large rollout. How to automate recurring sprint ceremonies in Jira Standups, retros and planning come round every sprint, but Jira won't create them on a schedule. Here's how to auto-create ceremony issues. How to create a monthly recurring task in Jira Jira has no built-in recurring issues. Here's how to create a monthly task that repeats on a set day, the last day, or first business day. How to create recurring tasks in Jira Jira has no native repeat button. Here are the three real ways to create recurring tasks in Jira Cloud, and when each one breaks down. How to create recurring Jira issues on business days (skipping weekends and holidays) Jira's scheduled automation fires on a fixed cron, with no concept of business days or holidays. Here's how to recur issues on working days only. How to create recurring Jira issues without using Automation executions Scheduling recurring issues with Jira Automation quietly spends your monthly execution limit — and that meter is changing. Recur issues off it.

Get Cadence

Free for up to 10 users, with one honest paid plan after. See pricing →

Get it on the Atlassian Marketplace →