Exporting and importing CSV, and sending feedback
Export schedules
On the schedule list, More, then Export, saves the schedules shown with the current filters as a CSV file, for example repeatwise-schedules-2026-10-07.csv. Each line has the name, project, status, the rule in words, the time zone, the next run (in UTC and in the schedule’s time zone), the last run (UTC, status and issue key), the owner and the labels.
The owner column says You for your own schedules and is empty otherwise: the list never receives other people’s names or account ids, so the file does not contain them either.
Import schedules
On the schedule list, More, then Import from CSV (or Import & export under RepeatWise in the Jira sidebar, or Import from CSV when you have no schedules yet), creates schedules from a CSV file: the RepeatWise template, a schedule export, or a sheet you filled in yourself. It is meant for moving rules from Jira’s “Set to recur”, other apps or spreadsheets (see Migrating).
- Get the template: under RepeatWise in the Jira sidebar, Import & export, then Download CSV template (or Copy template if your browser blocks downloads). It is also in the import dialog, and here without opening Jira. Fill one line per schedule and delete the three example lines.
- Pick the file, or paste its content and click Check pasted CSV. A file holds at most 200 schedules and 1 MB.
- Read the preview. Each line shows its status: Ready, Error (with the exact reason, for example
Issue type "Story" does not exist in OPS. Available: Task, Bug.), or Skipped when a schedule with the same name already exists in the same project, or appears earlier in the file. Tick Import anyway to create those too. - Click Create N schedules. Schedules are created one at a time with the same checks as the wizard: you need the same permissions, and you become the owner of each one. Stop finishes the current schedule and stops. The preview shows each result; a line that failed shows why.
- When schedules were created, choose Save import report: a CSV with one line per row of your file, what happened to it, and the next step (for a created schedule: stop the old rule it replaces, or both will create the same work).
Nothing is created for a line with an error. Fix the file and import it again: lines already created are skipped as duplicates, so nothing is created twice. Imported schedules start active, with no sub-tasks, sprint or custom fields; edit a schedule afterwards to add them.
The file is read in your browser; RepeatWise sends it nowhere else. Projects, issue types and priorities are matched against your Jira site exactly (key or name, case ignored). RepeatWise never guesses: a value that does not match is an error.
Template columns
Column names are not case sensitive, and the columns can be in any order. Unknown columns are ignored and listed in the preview. Put a cell that contains a comma in double quotes ("report,weekly"): a row with more or fewer cells than the header is an error.
| Column | Value | When empty |
|---|---|---|
| Name | Schedule name | The summary |
| Project key | Project key (or exact project name), for example OPS |
The project of the page (project page only); otherwise an error |
| Issue type | Issue type name or id, for example Task |
The project’s default standard type, shown in the preview |
| Summary | Summary of each issue; variables such as {{date}} work |
The name |
| Description | Plain text. Blank lines separate paragraphs | No description |
| Frequency | A sentence, for example every Monday at 9am or last business day of the month at 17:00 (the same phrases as Quick Start’s Describe it) |
Use Preset instead |
| Preset | daily, weekdays, weekly, every-2-weeks, monthly, monthly-last-business-day, quarterly, yearly or custom |
Use Frequency instead |
| Every | Custom preset only: a number and a unit, for example 3 months (days up to 365, weeks 52, months 24, years 10) |
|
| On | A weekday (MO to SU, or Monday) for weekly rules, or a day of the month (1 to 31) for monthly, quarterly and yearly rules |
The weekday or day of the start date |
| Weekend rule | keep, before (the Friday before) or after (the Monday after). Not for weekdays and monthly-last-business-day |
keep |
| Time | HH:mm, 24-hour |
09:00 |
| Time zone | IANA time zone, for example Europe/Paris |
Your browser’s time zone |
| Start date | YYYY-MM-DD, in the schedule’s time zone. Yearly rules repeat on this month |
Today |
| Labels | Comma separated, no spaces inside a label: report,weekly |
No labels |
| Assignee | owner or default (Jira’s default assignee for the project, unassigned if the project has none; unassigned is accepted too) |
default |
| Priority | Priority name, for example High |
Jira’s default priority |
| Holiday country | Optional 2-letter code, for example FR. Holidays move with the weekend rule; weekdays skips them |
Weekends only |
Use either Frequency or Preset (with Every and On) on a line, not both. If the sentence gives a time or a start date and the column gives another, the line is an error. A sentence the parser does not fully understand is an error, never a guess: use the preset columns for it.
Examples
Name,Project key,Issue type,Summary,Frequency,Preset,Every,On,Weekend rule,Time,Time zone,Start date,Labels,Assignee
Weekly team report,OPS,Task,Weekly report {{date}},every Monday at 9am,,,,,,Europe/Paris,2026-11-02,"report,weekly",owner
Month-end close,FIN,Task,Close the books for {{month}},,monthly-last-business-day,,,,17:00,Europe/London,2026-11-01,finance,default
Server patching,OPS,Task,Patch the servers,,custom,3 months,15,after,08:00,America/New_York,2026-11-15,,
Importing an export
A file made with Export can be imported again, for example to copy schedules to another project (change the project column) or another Jira site. Its Rule column is read as the frequency sentence and its Time zone and Labels columns are used; the other columns are ignored. An export has no issue type or summary, so the project’s default type is used and the summary is the name; add Issue type and Summary columns to choose them. Rules that the sentence cannot express (several weekdays, a position such as “the 2nd Tuesday”, end dates, advanced rules) and weekend or holiday settings do not come back: those lines show an error, or get the default weekend rule. Recreate them in the wizard.
Compliance report
Under RepeatWise in the Jira sidebar, Compliance report (or on the schedule list, More, then Compliance report…), pick a period (3 months by default, at most 12) and select Build report. For each schedule (of the project, on a project page), the report counts the occurrences planned in the period: created on time (within 15 minutes of the planned time, measured on the creation time Jira records for the issue), late (with the average delay), skipped or failed, and the on-time rate (on time / (planned - skipped)). Issues you cannot see have no known creation time: they show “time not visible” and are left out of the rate. It also reads, as you, whether each created issue was done by its due date (a done issue whose Jira resolution date is on or before its due date), done late or is overdue; issues with no due date in Jira are not judged, and issues you cannot see are marked “not visible”. Above 10,000 runs the report is partial: it is shown but cannot be saved, so choose a shorter period. Save CSV gives one line per occurrence; Save report gives an HTML file to open in your browser and print or save as PDF for an auditor. Everything is built in your browser from RepeatWise’s run history and Jira; nothing is stored or sent outside Jira. “Run now” occurrences are not included; dates skipped by a holiday or exception rule never became occurrences and are in the occurrence log.
Export run history
- One schedule: on its detail page, under Run history, choose Export run history.
- All schedules (administrators): on the administration page, under Occurrence log, choose Export run history.
Pick a period (dates in your time zone, at most 12 months), then Prepare file. Each line is one run: schedule, project, planned time in UTC and in the schedule’s time zone, status, issue key, whether it was a Run now, and the error or reason text. Runs are listed oldest first. You see the runs of the projects you can browse; administrators see every schedule.
A file holds at most 10,000 runs. When more exist, save the first part, then choose Prepare part 2: it starts right after the last run of part 1 (no run is missing or repeated), and so on until the period is complete. Files are named ...-part2.csv, ...-part3.csv. Runs of deleted schedules, and skipped dates that never became a run (holiday or exception skips, shown in the occurrence log), are not included.
Download or copy
The file is built in your browser. Download CSV saves it to your device; Copy CSV copies the same content to your clipboard, to paste into a spreadsheet, in case your browser blocks downloads from Jira apps. Nothing is sent anywhere else.
The file is UTF-8 with a byte order mark, so Excel shows accents correctly. A cell that starts with =, +, - or @ gets a leading ' so that a spreadsheet does not run it as a formula.
Feedback
Feedback (on the schedule list and the administration page) asks “How is RepeatWise working for you?” and offers:
- Rate RepeatWise on the Marketplace: opens the Atlassian Marketplace reviews in a new tab.
- Suggest a feature and Report a problem: open your own email app with a short template addressed to RepeatWise support. You review and send the message yourself. The template contains only the app version: no schedule content and no account id.
An option appears only when its destination is set up; the button is hidden when none is.
Review invitation
Once, at a good moment, the schedule list asks “How is RepeatWise working for you?”. It appears only when all of these are true:
- your oldest schedule was created at least two weeks ago, and the schedules you own have created at least five issues;
- none of your schedules is in error, and none had a failed run in the last seven days;
- you have not answered recently: Not now waits 30 days, Don’t ask again stops it for good.
It works well offers a link to the Atlassian Marketplace reviews. Could be better offers Contact support (your own email app, as above) so we can help, and the same review link: every answer can lead to a review. Leaving a review stops the invitation. Nothing is sent by the app; the invitation appears only once the Marketplace listing exists.