How can customers repeat a request from the Jira Service Management portal?
By Rolf Eriksen. Some requests come back every month: an access review, a report run, a supplies order. This page is for the service desk admin whose customers ask “can I just raise the same one again?” Disclosure: Eriksen Labs makes Recurring Requests & Templates for Jira Service Management, one of the options below.
Short answer
Jira Service Management Cloud has no button that lets a portal customer repeat or schedule a request they raised before. The customer can raise a new request by hand. An agent or admin can make work repeat with Jira Automation or Set to recur, but then the agent's flow owns the schedule, not the customer, and each run counts toward the site's Automation usage. An app can give customers a Request again action in the portal.
The options
| Option | Who sets it up | Raised as | Where it stops |
|---|---|---|---|
| Raise it again by hand | The customer, each time | The customer | Form answers are typed again; easy to forget |
| Set to recur, on a work item | Anyone with view and edit permission on the work item (not portal customers) | A clone made by Automation | Daily, weekly, every weekday or every two weeks; does not copy attachments, web links or linked items; counts toward Automation usage |
| Automation flow with a scheduled trigger | A space admin or Jira admin | The flow's actor | One clock per flow; no request type on a clone; counts toward Automation usage |
| Recurring Requests & Templates (our app) | The customer, in the portal, once an admin enables it | The customer | No files, participants or record-picking fields copied; Jira Service Management Cloud only |
Atlassian's own pages on Automation triggers and how usage is counted have the details. Our guide to recurring tickets after Automation step billing does the arithmetic per job, with a calculator, and says when Automation is the better choice: whenever an admin, not the customer, should own the recurrence.
Request again, in the portal
With Recurring Requests & Templates for Jira Service Management, a customer opens a request they already raised and chooses Request again. They can raise it now, set it to come back daily, weekly or monthly at a time they pick in their own time zone, or save it as a template to raise later in one click.
- Requests are raised as the customer, follow the request type's workflow and count toward your SLAs like one they typed.
- Attached forms carry across with their answers. Files, participants, organization sharing and fields that point at another record (such as Affected services) are not copied; the app tells the customer about files and names the record fields left blank.
- Scheduling is off until a project admin turns it on, with limits on which request types may repeat, how often, for how long, and how many schedules one customer may have.
- A schedule that fails three times in a row pauses itself and says why.
- It runs on Atlassian Forge and sends nothing outside Atlassian. It is also listed in Atlassian Isolated Cloud (which of our apps are where).
Questions
Can a Jira Service Management customer repeat a request from the portal?
Not with Jira Service Management alone. The portal has no action that raises a past request again or schedules it. Customers raise a new request by hand, or an agent sets up Automation. The Recurring Requests & Templates app adds a Request again action to the portal.
Can customers schedule their own recurring requests in Jira Service Management?
Not natively: Set to recur and Automation flows are built by people with edit permission or admin rights, and portal customers have neither. With Recurring Requests & Templates, a customer can set a request to come back daily, weekly or monthly, once an admin enables scheduling.
Does a recurring request count toward Automation usage?
A request repeated by Set to recur or an Automation flow does, because a flow raises it. Recurring Requests & Templates raises the request itself, without a flow. Rules of your own that react to new requests still run, as they would for any request.
Is the repeated request raised as the customer?
With Recurring Requests & Templates, yes: it appears in the queue attributed to the customer who scheduled it and counts toward SLAs like any request they raise. A clone made by Automation is created by the flow.