RepeatWise user guide
RepeatWise creates Jira issues on a repeating schedule: every Monday, on the last business day of the month, every quarter, and so on. In a Jira Service Management project it can raise customer requests instead.
| Page | What it covers |
|---|---|
| Getting started | Quick Start, sentences, and quick templates |
| How to create recurring issues in Jira Cloud | Jira Automation and RepeatWise setup |
| Recurring issue on the last business day | Nth weekdays and holiday-aware dates, with a France example |
| Recurring issues with sub-tasks and sprints | Sub-tasks, sprint assignment and previous-issue rules |
| The 4-step wizard | More options and every field, step by step |
| Frequencies and examples | Daily, weekly, monthly, yearly |
| Time zones and daylight saving | How clock changes are handled |
| Holidays and business days | Calendars, policies, month-end rules |
| Holiday country list | Countries and territories in the picker |
| Early creation and exceptions | Creating issues ahead of the due date |
| Chaining, sprint and sub-tasks | What happens to the previous issue, sprints, sub-tasks |
| Service requests | Raising Jira Service Management requests on a schedule |
| Variables | {{date}}, {{month}}, {{number}} and more |
| RepeatWise in Rovo chat | Suggestions and schedules from a chat message |
| Where to find RepeatWise | Entry points, schedule list, detail page, and Duplicate |
| Permissions | Who can create, the owner, reassigning |
| Errors and what they mean | Messages, retries, catch-up |
| Administration | Settings, schedules in error, log |
| Export and feedback | CSV export of schedules and run history, CSV import of schedules, the Feedback dialog |
| Data and privacy | Runs on Atlassian, what is stored |
| Migrating to RepeatWise | From “Set to recur”, The Scheduler, Recurring Tasks |