OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appCustomers repeat a portal request on a schedule or from a saved template — recurring tickets set up in seconds, no cron
Customers schedule their own repeat requests
On a request they raised, a customer picks Request again, then Repeat on a schedule: every 3 months at 09:00 in their own time zone. It is raised as that customer, so it reaches your queue and counts towards SLAs.
Raised as the customer, no Automation rule needed
When a schedule is due, the app raises the request as the customer, into your queue. No Automation rule, no steps of its own. From 3 Dec 2026 Atlassian bills steps over your allowance only where extra usage is on.
You limit what repeats, how often and how long
Scheduling stays off until a project admin turns it on. Set the shortest gap between repeats, when every schedule stops, how many each customer may have at once, and which request types may repeat.
Supporting media
More details
Access reviews, monthly reports, recurring maintenance: raised by hand, and forgotten.
A customer opens a request they raised and chooses Request again — raise it now, save it as a template, or repeat it in their own time zone: daily, weekly, monthly, quarterly, or on the first Monday, the 2nd working day or the last day of the month. They see the next dates before saving.
A 09:00 schedule stays at 09:00 through daylight saving.
Requests are raised as the customer: they follow your workflow, count towards SLAs and carry the form's answers. No Automation rule or steps of its own.
Portal customers need no agent licence.
Raise it now and templates work from install. Scheduling stays off per project until an admin turns it on. Admins limit what repeats, how often, how long and how many per customer, set closed days (a run due on one moves to the next open day, or is skipped), and can pause or stop any schedule.
Built on Atlassian Forge. No data leaves Atlassian.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Recurring Requests & Templates for Jira Service Management integrates with your Atlassian app
Version information
Version 3.5.0•for Jira Cloud
- Release date
- Oct 20th 2026
- Summary
- Monthly patterns, quarterly, chosen weekdays, closed days and a date preview
- Details
- Monthly schedules can follow a pattern, such as the first Monday, the 2nd working day or the last day of the month, every month or every few months.
- How often adds Quarterly (every 3 months); the other choices are unchanged.
- Weekly schedules can run on chosen days, such as Monday and Thursday, where the project's shortest gap allows it.
- Before you save, the form lists the next dates, any moved or skipped for a closed day, and when the schedule stops.
- Project admins can set the desk's closed days. A run due on one moves to the next open day, Monday to Friday, or is skipped if the admin chooses; no run moves earlier. Saving them moves the next runs they touch, and raises nothing.
- While scheduling is off, Getting started also offers to turn it on with a shortest gap of 1 day, which chosen weekdays need. The default stays 7 days.
- Schedule cards name the pattern, such as "First Monday of every month".
- No new permissions. Nothing leaves Atlassian.
- Payment model
- Paid via Atlassian
- License type
- Commercial