Where to find RepeatWise
| Where | What | Status |
|---|---|---|
| Global page (Jira sidebar, Apps, “RepeatWise”) | Your schedules across the projects you can browse. Select RepeatWise to show its pages: Schedules, Calendar, Find recurring work, Compliance report, Import & export, Preferences, Getting started | Available |
| Project page (project sidebar, “RepeatWise”) | Schedules of that project; new schedules start on that project | Available |
| Administration (Jira settings, Apps, “RepeatWise”) | Overview (summary tiles, schedules in error), Settings, Occurrence log; a Get started button in Manage apps. Jira administrators only | Available |
| Issue action “Make this issue recurring” | Open Quick Start filled from the issue; More options opens the wizard | Available |
| Issue panel on generated issues | Show the schedule, occurrence number and next run, with a link to the schedule | Available |
The issue action copies the project, issue type, summary, labels, priority, components, unreleased fix versions and parent where available, and the description exactly as it is in the issue: formatting, checklists, tables, panels, images and mentions included (content the editor cannot edit is kept as is and shown read-only). The assignee is copied when that person can still be assigned in the project. Mentions in the description notify people every time an issue is created: RepeatWise warns you about them. Attachments are not copied. Tick Also link each new issue to KEY to give every new issue a Relates link to the source issue.
The schedule list and detail page
The list starts with a What do you want to repeat? box: type a sentence such as Weekly report every Monday at 9am (English or French) and select Create. Quick Start opens with the sentence already understood (frequency, day, time, summary) by RepeatWise’s own sentence reader, which runs in your browser: no AI service, nothing leaves Jira. You check every value before saving. Below it, one line counts how many issues the active schedules will create Today, Tomorrow and This week (the next 7 days, in your time zone), with View calendar. Each card starts with a small calendar page that says what repeats, for example WEEKLY / THU, MONTHLY / LAST or YEARLY / MAR: blue for daily, teal for weekly, purple for monthly or quarterly, magenta for yearly, orange when the schedule needs attention, grey when it is paused or ended. The card then shows the schedule’s name and project, the next run in bold with its city and UTC offset (for example 09:00 Casablanca (GMT)), the same moment on your own clock when it differs (10:00 for you (Madrid)), how often it repeats, and the last run with a coloured dot (green created, red failed, grey skipped), or Not yet and when the first run comes. Active schedules show no status badge; Paused, Ended or Error schedules do. A schedule that needs attention gets an orange card, a Needs attention badge and one line with the problem and Review, which opens its detail page; when there are any, a line above the list counts them with Show. Select a schedule’s name to open its detail page. You can search by name, project, label or frequency, filter by project and by status (All, Active, Needs attention). The More menu shows Paused or Ended schedules, opens the Owner and label filters (only Mine, or one label), and holds Select schedules…, Export, Import from CSV and Find recurring work… (finds the work that already comes back on a calendar in a project’s issues and sets it up in one click, see Migrating). Each card has Edit; Pause or Resume, Duplicate and Delete are in its More actions menu (•••). To pause, resume or delete several schedules at once, choose More, Select schedules…, tick them (or Select all matching) and use Pause selected, Resume selected or Delete selected (it asks you to confirm; issues already created are kept), then Done: each schedule is checked on its own, and the result lists any that failed. Long lists show 50 schedules at a time; Show more adds the next ones.
The detail page starts with a breadcrumb (RepeatWise > Recurring schedules > the schedule’s name), the schedule’s name and one line taken from the issue description (or its summary). A header card shows the status, a health badge (Healthy, or Needs attention with an orange card when the schedule has a problem or its last run failed), the recurrence, the project and the next run. When the schedule acts on the previous issue (for example If previous issue is still open: Skip), the card says so. The card has Run now, Edit, Pause or Resume, and a More actions menu with Duplicate and Delete.
History lists who created, edited, paused, resumed, reassigned or used Run now on the schedule, when, and for an edit what changed (for example Time: 08:00 -> 09:00); Export history saves it as CSV. People are named; account ids are never shown. The history of a schedule is kept as long as the schedule exists.
Upcoming runs lists the next planned runs (date, then time and time zone city); Run history lists the last 20 occurrences, newest first, with the date, a link to the created issue and a status (Created, Skipped, Failed or Pending), plus the reason for a skip or a failure. Each list shows four rows; View all shows the rest.
Run now creates this schedule’s issue immediately, after you confirm. The regular plan does not change: the next run stays where it was. It works on an active or a paused schedule (a paused one stays paused), when the app license is active, for the schedule’s owner or a Jira administrator. The issue is created by the schedule owner, exactly like a planned one: the variables (such as {{date}}) and the due date use today’s date in the schedule’s time zone, and the sub-tasks, the sprint and the comment or transition on the previous issue are applied. The rule “skip if the previous issue is still open” does not stop a run you asked for. The run shows in Run history with a Run now tag. A second click in the same minute does not create a second issue, and a new run is possible one minute after the previous one. Run now is not available in the minute the schedule’s own run is planned. Run now makes one attempt: if Jira refuses the issue, the run is marked Failed with the reason, and you can try again. If Jira does not answer clearly (for example it is unavailable), the run stays Pending: a few minutes later RepeatWise checks whether Jira created the issue and records it, or marks the run Failed so you can run it again. It never creates a second issue for the same run.
Duplicate opens a new, prefilled schedule in the wizard. If the source start date is in the past, the copy keeps the rule’s rhythm and starts on the next aligned date (or today if none remains), rather than restarting its interval from today. The copy is named Copy of followed by the original name. A future start date stays as set. If an end date is before the copy’s start date, the end rule is cleared. Review the copy and select Save to create it. Individual skipped or moved dates are not copied.
| Status | Meaning |
|---|---|
| Active | Running. If the last attempt failed, a warning shows the retry time. |
| Paused | Not running. Resuming starts from now: paused periods are not caught up. |
| Error | Stopped. The message says why. Fix it and save the schedule to restart. |
| Ended | The rule has no more occurrences. |
Calendar
Select Calendar under RepeatWise in the Jira sidebar, or View calendar at the end of the Today, Tomorrow and This week line to see every run on a calendar. On a project page it shows only that project’s schedules; View in calendar under a schedule’s Upcoming runs shows only that schedule (Show all schedules widens it). Choose Month, Week or Agenda (a list by day of one week, Monday to Sunday; the default on narrow screens), move with Today and the arrows (by month, or by week in Week and Agenda), and filter by project, Mine or Everyone, and label. Paused schedules are left out unless you turn on Include paused schedules. All times are in your time zone, shown at the top.
Past days show what happened, with the status (Created, Skipped, Failed or Pending) and the issue key. Today and later days show the planned runs, each in its schedule’s color; a run created early shows on its creation day, with the due date in its details. A run skipped for a weekend, holiday or exception is shown struck through, with the reason. A month day shows three runs, then +N more: select the day (or press Enter on it; the arrow keys move between days) to list all its runs with links to the issue and to the schedule. When a period has too many runs to show, a message says some are not shown: filter to see fewer schedules. Back returns to where you opened the calendar; where Jira supports it, your browser’s Back button does too.
Finding generated issues
Each created issue carries a property recurrence with scheduleId, occurrence and plannedAt. In JQL:
issue.property[recurrence].scheduleId = "<schedule id>".
Preferences
Under RepeatWise in the Jira sidebar, Preferences sets how RepeatWise looks for you: a 12-hour or 24-hour clock, weeks starting on Monday or Sunday in the calendar, the time zone and project proposed when you create a schedule, whether the schedule list opens on every schedule or only yours, and the calendar’s first view (Month, Week or Agenda). They are saved in this browser for your Jira account: another browser keeps its own, and nothing is sent anywhere. Exported files keep the 24-hour clock. Site-wide defaults (who can create schedules, default time zone and holiday country, catch-up window) are set by Jira administrators in the administration.