Cadence: Recurring Work for Jira

Recurring work items on a schedule you control.

Cadence creates Jira work items on a schedule. Unlike Jira's built-in recur option, which hides a clone automation inside a single work item, every schedule on your site lives on one dashboard where anyone can see what recurs, when it next runs, and what it has created.

Getting started

Open Apps › Cadence: Recurring Work from the Jira navigation.
Select + New schedule.
Give the schedule a name, choose the project and work type, and write the summary and description the created items should carry.
Build the recurrence rule, check the preview of the next six occurrences, and save.

The dashboard

Every schedule on the site appears here with its rule, next run time, how many items it has created, and a link to the most recent one. From each row you can pause a schedule, skip only its next occurrence, run it once immediately without changing the schedule, edit it, or delete it. Deleting a schedule never touches the work items it already created.

Building a rule

Rules are built from plain controls, never cron. Choose daily, weekly on specific weekdays, every two weeks on specific weekdays (pick the date of the first week, and the schedule keeps to alternate weeks from there), or monthly on a chosen day of the month, which clamps sensibly in shorter months. Pick the time and the timezone; the timezone defaults to your Jira profile and is stored with the schedule, so daylight saving changes are handled correctly. Optionally restrict a schedule to working days: it then skips the days and holidays a Jira administrator has excluded (Monday to Friday with no holidays unless changed), and a monthly schedule that lands on one moves to the next working day. As you build, a live preview lists the next six occurrences.

What gets created

Each occurrence is created fresh from your template rather than cloned. The summary and description support a {date} token that resolves to the creation date. You can set labels, assign the created item to yourself, and define subtasks that are created alongside the parent. Due dates can be left off, set to the day of creation, set to the day before the next occurrence, or set a number of days after creation.

Making an existing item recurring

Open any work item and expand the Cadence panel, then choose Make recurring. That item becomes the template, and the panel shows the resulting schedule with controls to pause, skip, edit or remove it. A single work item can carry more than one schedule.

Timing

Schedules are evaluated every five minutes, so an item appears within about five minutes of its scheduled time. Cadence does not consume your Jira automation limits.

Administrator settings

Site administrators can set an accent color used for buttons and highlights, the naming template applied when a work item is made recurring (default Recurring: {summary}), and the working-day calendar: which weekdays count as working days and a list of holiday dates. Schedules marked working days only follow that calendar. Jira has no site-wide working-day setting an app can read, so this one is kept in Cadence.

Permissions and data

Cadence reads and writes Jira work items in order to create the items you scheduled, stores its schedules in Atlassian Forge hosted storage, and reads user information so it can show who created a schedule. Display names are looked up live and never stored. The app declares zero external network egress.

Support

Questions or problems: support@helzbrand.com