Switching to RepeatWise in 5 minutes

RepeatWise cannot read the rules of another tool: no app can read Jira’s “Set to recur” rules, and other apps keep theirs to themselves. But it can read their results, the issues they created. The quick path, whatever you used before:

  1. Find recurring work (below): RepeatWise finds the work that already repeats and sets each one up in one click.
  2. For what it does not find, import a spreadsheet (one line per rule, the frequency in words) and save the import report.
  3. Pause the old rules before their next date, and check the first RepeatWise issues in the run history.

Then the detailed guides: Jira’s built-in “Set to recur”, The Scheduler, and Recurring Tasks.

The fastest way: Find recurring work

Under RepeatWise in the Jira sidebar, choose Find recurring work (or on the schedule list, More, then Find recurring work…), pick a project and select Find recurring work. RepeatWise reads the issues of that project created in the last 12 months (up to 600, only the ones you can see; nothing is stored) and lists the work that comes back on a calendar, whoever created it: by hand, by Jira’s “Set to recur”, or by another app. For each one you see how often it comes back (every day, every weekday, weekly on Monday, every 2 weeks, monthly, at the end of the month, every 3 months), its usual time, how many times and since when, and the last issue keys. Set it up opens Quick Start filled with that rhythm, time, issue type and a summary whose dates and numbers became variables (Weekly report {{date}}). Check it, create it, then turn the old rule off. Issues RepeatWise created are left out. Work needs at least 3 regular occurrences (a week of them for daily work).

Two details are kept from what was found. Every-working-day work follows the days the issues were created on: if they were created Sunday to Thursday but your holiday country works Monday to Friday, Quick Start says so, so you can pick the right country. Work every 2 weeks or every 3 months keeps its weeks and months: the start date is the next date in step with the old issues (a quarterly review of January, April, July and October stays there).

For rules this does not find (yearly work, irregular rules, rules that have not run yet), recreate them in the wizard (or with Make this issue recurring on an existing issue), or list them in a spreadsheet and import them as CSV, up to 200 at a time.

Before you start (all sources)

  1. List your existing recurring rules: name, project, issue type, frequency, time, assignee, labels.
  2. Create the RepeatWise schedule (see Getting started) and check the next 10 dates on the Review step against the old rule.
  3. Run both in parallel only if you can tolerate duplicates for one cycle, otherwise pause or delete the old rule just before the first RepeatWise date.
  4. Set the start date to the first date you still need. RepeatWise never creates issues for dates before the start date.

Concept map

| Concept | Jira “Set to recur” | The Scheduler | Recurring Tasks | RepeatWise | |—|—|—|—|—| | A recurring definition | Recurrence on an issue (a hidden automation rule) | Scheduled issue or template | Recurring task | Schedule | | Source content | The original issue is cloned | Template issue | Template or task | Issue template stored in the schedule (project, type, summary, description, assignee, priority, labels, sub-tasks) | | Frequency | Daily, weekly, business days, every 2 weeks | Wizard or cron | Wizard or cron | Daily, weekly, monthly (date or position), yearly; every N; cron or RRULE | | Time and zone | Not set in the simplified UI | See its documentation | See its documentation | Per schedule, IANA zone, daylight saving handled | | Holidays | Business days only | See its documentation | See its documentation | Country and region calendars plus your own days | | Cron | No | Yes | Yes | Yes, plus RRULE (limits) | | Variables | No | Yes | Varies | {{date}}, {{due}}, {{day}}, {{month}}, {{quarter}}, {{year}}, {{week}}, {{number}}, {{schedule}} | | Overview | In the issue only | Per app | Per app | Global list, project list, admin log |

Third-party product features change; check your current version when mapping.

From Jira “Set to recur”

Set to recur is a Jira feature, not an app, so nothing needs to be uninstalled. Rules are hidden automation rules that clone an issue.

There is no automatic import of the rules: Jira gives apps no way to read Set to recur rules. Start with Find recurring work (above): it finds the issues those rules created and sets each one up in one click. For the others, a spreadsheet is the fastest way:

  1. Download the CSV template, or in RepeatWise open Import & export in the Jira sidebar and choose Download CSV template.
  2. For each recurring issue, add a line: name, project key, issue type, summary, description, and the frequency in words (for example every weekday at 9am or every 2 weeks on Monday). Set Time zone and Start date to the next date you want.
  3. Import the file, read the preview, fix the lines with errors, then Create.
  4. Choose Save import report: one line per row with what happened (created, skipped as a duplicate, error) and the next step.
  5. Turn recurrence off on each source issue in Jira, so only RepeatWise creates issues.

See Import schedules for every column.

Steps, one rule at a time

  1. Open an issue that recurs and note its frequency, the fields you rely on, and the copied children.
  2. In RepeatWise, click New schedule. Pick the same project and issue type; copy the summary and description into the fields. Add variables such as {{month}} if you want distinct titles.
  3. Set the frequency. Monthly, quarterly and business-day patterns are available; set the time and time zone explicitly.
  4. Set the start date to the next date you want.
  5. On the source issue, turn recurrence off in Jira so only RepeatWise creates issues.

What is different

From The Scheduler

  1. Export or list each scheduled issue: project, type, fields, cron or wizard settings, variables.
  2. Recreate each as a RepeatWise schedule. Simple cron patterns map to the wizard (for example 0 8 * * 1 is Weekly, Monday, 08:00). Others can be pasted as an advanced rule (at most 24 issues a day, 60 minutes apart).
  3. Translate variables using the table below.
  4. Add a holiday country and policy if you handled holidays by hand.
  5. Disable the old scheduled issue after checking the 10-date preview.

Variables | Typical variable | RepeatWise | |—|—| | Current date | {{date}} or {{date:FORMAT}} | | Month, year | {{month}}, {{year}} | | Quarter | {{quarter}} (Q1 to Q4) | | Week number | {{week}} | | Day of the month | {{day}} | | Due date | {{due}} |

Check the exact names your version used; unknown variables are left as typed, which makes leftovers easy to spot in the preview.

What is different

From Recurring Tasks

  1. List each recurring task: project, type, frequency, time, time zone, assignee.
  2. Recreate it in RepeatWise, entering the time zone explicitly on the When step.
  3. Compare the 10-date preview, including days around a clock change, with what you expect.
  4. Delete or pause the old task once the first RepeatWise issue has been created (or just before it is due).

What is different

Checklist after migrating