Administration
Jira settings, Apps, RepeatWise, with three pages in the sidebar: Overview (the summary tiles and the schedules in error), Settings and Occurrence log. In Manage apps, Get started opens a short checklist with the settings, for the first setup. Visible to Jira administrators only; every action is checked again on the server.
The admin page starts with three summary tiles: Active schedules, Issues created this month (UTC), and Schedules in error. The monthly count uses UTC calendar boundaries. Below them are settings, schedules in error and a global occurrence log. The global RepeatWise page lists schedules in projects the viewer can browse.
Settings
| Setting | Options | Default |
|—|—|—|
| Who can create schedules | Project administrators, or everyone with “Create issues” in the project | Project administrators |
| Default time zone | Any IANA zone, or each user’s own zone | Each user’s own zone |
| Default holiday country | Two-letter code such as FR, or empty for weekends only | Empty |
| Catch-up window (hours) | Whole number, 0 to 72 | 24 |
| Email owners when a schedule fails | On or off | On |
The owner of a schedule always needs “Create issues” in the project. Settings apply to new schedules and to the next scheduler run.
Email owners when a schedule fails. When a schedule stops with an error, Jira sends its owner a notification about the last issue the schedule created. Jira sends it with its own notification system, so RepeatWise uses no email service and no data leaves Atlassian. See Errors.
Schedules in error
Lists schedules that stopped, with the reason. Reassign owner searches users who can create issues in the project and gives the schedule to one of them.
Occurrence log
The 100 most recent occurrences across all schedules, filterable by status and project key.
| Status | Meaning |
|---|---|
| Created | Issue created on time (within 15 minutes). |
| Created late | Created after a retry or catch-up. |
| Waiting | Reserved; attempt in progress or waiting for a retry. |
| Failed | Gave up (4 attempts, too late, or the rule changed). |
| Skipped | Not created on purpose. |
Skipped dates also appear with their cause: holiday policy, exception, day missing in the month, merged into an earlier occurrence, catch-up window expired, schedule paused or stopped by an error (written when it is resumed, saved or reassigned), or previous issue still open (when the schedule is set to skip). The log can also show a date not created while the app license was inactive. Occurrence and candidate log rows are removed after 24 months.
Export run history saves every run of a period (at most 12 months, at most 10,000 rows) as a CSV file. See Export and feedback.