Simple Recurring Issues

Make any Jira issue repeat — with its subtasks. Pick a day and an hour, not a cron expression.

What it does

Jira can already repeat work through its built-in Set to recur option, but the schedule ends up inside an automation flow (Project settings, Automation, filtered by the label Recurring), where nobody can easily find it again. Standups, weekly reports, release checklists and monthly reviews are the kind of work people want to see and adjust.

This app takes an issue that is already set up the way you like and recreates it on a schedule you choose, with all of its subtasks. The schedule stays on the issue itself, with the next run time and a history of what it created.

Not sure you need an app? The comparison guide covers the built-in option and when it is the better choice.

Setting it up

There is no setup. Install the app and it appears on every issue.

Making an issue repeat

1. Open the issue you want to repeat.
2. In the Details sidebar on the right, expand Repeat.
3. Choose how often: every day, every weekday, every week on a chosen day, or every month on a chosen date.
4. Choose the hour, and the timezone. The timezone is filled in from your own Jira profile.
5. Click Start repeating.

Each copy is created with the original's summary, description, issue type, priority, labels, assignee, and every subtask with its own summary, description and assignee.

Managing repeats

Go to Apps → Recurring Issues to see every repeat on the site, when each one next runs, and what it last created. Any repeat can be paused and resumed, or deleted. Repeats are shared across the site.

When it runs

The app checks once an hour. A repeat set for 09:00 is created during the 09:00 hour in the timezone you chose, not necessarily on the exact minute — Atlassian spreads scheduled work across the hour.

Creating a repeat never creates an issue immediately. If you set up a 09:00 daily repeat at 09:30, the first copy appears the following day.

Timezones, daylight saving and month ends

Schedules are evaluated in the timezone you picked, so they do not drift when the clocks change.

• On the day the clocks go back, an hour occurs twice locally. A repeat set for that hour runs once, not twice.
• On the day the clocks go forward, an hour does not exist locally. A repeat set for that hour is skipped for that day rather than firing at the wrong time, and resumes normally the next day.
• A monthly repeat set for the 29th, 30th or 31st runs on the last day of shorter months, rather than silently skipping them.

Missed runs

If a run is missed — an outage, or the app being reinstalled — the app creates one catch-up issue rather than one for every missed slot, so a quiet period does not flood your backlog.

Who the issues are created by

Scheduled work in Jira runs without a signed-in person, so each recurring issue is created by the app itself. The Reporter on the created issue is shown as Simple Recurring Issues. The assignee is copied from the original issue.

What this version does and does not do

Included: summary, description, issue type, priority, labels, assignee, and subtasks with their own summaries, descriptions and assignees. Pause, resume and delete.

Not included yet: custom fields, attachments, comments, linked issues, components, fix versions, repeats that stop after a set number of runs, and repeats on a specific minute. These are on the roadmap. They are listed here so nobody installs the app expecting them.

Permissions the app requests

Scope	Why it is needed
read:jira-work	Read the issue being repeated, and its subtasks
write:jira-work	Create each recurring issue and its subtasks
read:jira-user	Resolve an assignee when a project refuses unassigned issues
storage:app	Store schedules in Atlassian-hosted Forge storage

Support

Email support@harvizzle.com. Target first response is two business days, Monday to Friday. Please include your Jira site URL, the issue key, and what you expected to happen.

There is no separate support portal to sign up for, and no ticket number to chase.