Skip to content
PokutsoftPokutsoft

Recurring Issues - Documentation

Updated: 2026-06-30

Overview

Recurring Issues creates Jira issues on a schedule. Unlike native automation, it understands a working calendar (weekends and holidays), runs each schedule in its own timezone, accepts schedules written in plain English, and creates issues with full fidelity (sub tasks, due dates, assignees and custom fields). It runs entirely on Atlassian Forge, so your data never leaves Atlassian.

Getting started

  1. Install the app from the Atlassian Marketplace onto your Jira Cloud site.
  2. Open a project and go to the Recurring Issues page from the project sidebar.
  3. Create a schedule. Give it a name, choose how often it runs, describe the issue to create, and press Preview next runs to check the dates before saving.

Scheduling

Choose a frequency and a time. Each schedule keeps its own timezone.

FrequencyOptions
DailyRuns every day at the chosen time.
WeeklyPick one or more weekdays.
MonthlyA fixed day of the month, or a working day rule (first, last or nth working day).

The time you set is interpreted in the schedule's timezone, not UTC.

Working calendar

When a scheduled run lands on a weekend or a holiday, you decide what happens:

  • Do nothing — create it anyway.
  • Skip that run — no issue is created.
  • Move to the previous working day.
  • Move to the next working day.

Holidays come from a holiday calendar. An admin creates calendars on the Recurring Issues Admin page, either by entering dates or by importing an ICS file. You then attach a calendar to a schedule.

Plain English schedules

In the schedule form, type something like every last working day of the month and press Interpret. The app fills in the frequency fields for you. This uses Atlassian's built in Forge AI, so the text stays inside Atlassian. Always review the fields it fills in before saving.

The issue that gets created

FieldWhat it does
SummaryUse the {date} token to insert the run date, for example "Weekly report {date}".
Due date offsetSets the due date to the run date plus the number of days you enter.
AssigneesEnter one or more account ids; the app rotates through them on each run.
LabelsApplied to every created issue.
Sub-tasksOne summary per line; each becomes a real sub task under the created issue.
Create in advanceCreate the issue a number of days before its target date.

Duplicate protection

Turn on Don't create a new one while an open instance still exists to avoid a backlog of copies. Before each run, the app checks whether a previous instance of the same schedule is still open and, if so, skips the run.

Managing schedules

  • Preview next runs before saving to confirm the dates.
  • Enable or disable a schedule at any time.
  • Run now to create an issue immediately, on demand.
  • History records what each schedule created, and when.
  • The Admin page manages holiday calendars and lists every schedule across the site.
How runs happen. The app checks schedules on an hourly cycle and creates any issues that are due. Because scheduled work has no user, those issues are created by the app. Everything you do in the UI (including Run now) is performed as you, within your own permissions.

Permissions & data handling

Scopes requested (least privilege):

  • read:jira-work — read project metadata and check for open instances.
  • write:jira-work — create the recurring issues and their sub tasks.
  • storage:app — store schedules, holiday calendars and run history.

The app runs entirely on Atlassian Forge with no external calls. Holiday data is defined by an admin or imported from ICS, never fetched from a third party. Plain English parsing uses Atlassian's Forge AI. Your data never leaves Atlassian and nothing is used to train any model.

Privacy, terms & support