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
Schedule the request instead of remembering it
A customer opens a request they already raised and picks how often it should come back: daily, weekly or monthly, at a time in their own timezone. Or saves it as a template to raise again in one click.
You decide who can, how often, and for how long
Recurring requests stay off until you switch them on, per project. Choose which request types qualify, the shortest gap allowed between repeats, how far ahead a schedule may run, and how many each customer may have.
Raised as the customer, not as the app
Every scheduled request is attributed to the person who asked for it, follows your workflow and counts towards your SLAs. Customers pause or cancel their own, and you can stop any schedule in the project.
Supporting media
More details
First release.
A customer opens a request they have already raised and can:
- Raise it again immediately
- Repeat it daily, weekly or monthly, at a date and time in their own timezone, optionally stopping after a set number
- Save it as a template to raise again later in one click
Scheduled requests are created as the customer who asked for them, so they arrive attributed to that person, follow your workflow and count towards your SLAs. Attached forms carry across with their answers, including choice questions and table rows.
Recurring requests are off until a project admin turns them on. Admins choose which request types may repeat, the shortest gap allowed, how far ahead a schedule may run and how many each customer may have, and can stop any schedule. Customers pause or cancel their own from the portal.
Known limitations: attachments are not copied, and a field referencing another record, such as Affected services, is left blank and named so it can be chosen again.
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 2.11.0•for Jira Cloud
- Release date
- Aug 1st 2026
- Summary
- Customers schedule their own recurring requests, with the controls you set
- Details
First release.
A customer opens a request they have already raised and can:
- Raise it again immediately
- Repeat it daily, weekly or monthly, at a date and time in their own timezone, optionally stopping after a set number
- Save it as a template to raise again later in one click
Scheduled requests are created as the customer who asked for them, so they arrive attributed to that person, follow your workflow and count towards your SLAs. Attached forms carry across with their answers, including choice questions and table rows.
Recurring requests are off until a project admin turns them on. Admins choose which request types may repeat, the shortest gap allowed, how far ahead a schedule may run and how many each customer may have, and can stop any schedule. Customers pause or cancel their own from the portal.
Known limitations: attachments are not copied, and a field referencing another record, such as Affected services, is left blank and named so it can be chosen again.
- Payment model
- Paid via Atlassian
- License type
- Commercial