RepeatWise in Rovo chat
If your site has Rovo, RepeatWise adds a RepeatWise agent to Rovo chat. Use it to find work you repeat by hand and to set up a schedule with one sentence.
What you can ask
| Ask | What happens |
|---|---|
| “What recurring work could I automate in project OPS?” | RepeatWise reads the issues created in OPS in the last 120 days, as you, and lists up to 5 summaries that come back every week, every 2 weeks or every month, with a suggested frequency. |
| “Create a weekly report every Monday at 9:00 in OPS” | The agent asks for anything missing, describes the schedule in one sentence and asks you to confirm. After your yes, it creates the schedule and shows the next 3 dates. |
| “List my recurring schedules” (or “in project OPS”) | The schedules you can see, with their frequency, next run and status. |
Frequencies available from chat
Every day, every weekday (Monday to Friday), every week on one day, every 2 weeks on one day, every month on a day (1 to 31; shorter months use their last day), the last business day of every month, every 3 months on a day, every year on a date.
Defaults: 09:00, your time zone, starting today (the first issue is the next matching date), issue type Task. Use variables such as {{date}} or {{month}} {{year}} in the summary so each issue has a distinct title.
For anything else (several weekdays, holidays, sub-tasks, sprints, assignee, description, edit, pause or delete), open Apps > RepeatWise in Jira and use the wizard. Cron and RRULE rules are available in the wizard (Advanced frequency), not in Rovo. Jira Service Management service requests are set up in the wizard only; Rovo creates Jira issues.
Good to know
- Schedules created from chat are the same as the ones created in the wizard: you are the owner, issues are created as you, and the same permissions apply.
- Rovo always asks you to confirm before RepeatWise creates a schedule.
- The analysis of your issues reads only their summary and creation date, as you (you only see suggestions from issues you can see). Nothing is stored, and nothing leaves Atlassian. Issues RepeatWise created are ignored.