Service requests (Jira Service Management)
In a Jira Service Management service project, a schedule can raise a customer request of a chosen request type instead of creating a Jira issue: a monthly access review request, a weekly backup check in the IT help desk, a quarterly laptop inventory, and so on.
Set it up
- Open the wizard (More options from Quick Start, or Create schedule) and choose a service project in step 1.
- Under Create, choose Service request. This choice only appears when the project is a service project you can see.
- Pick the Request type. Its description from the portal is shown under the picker.
- Fill in the summary and, if you want, the description. Variables work in both.
- Priority, labels and the due date (days after the occurrence date) appear when the request type has these fields.
- Continue with When, Rules and Review as usual. The review shows “Service request: request type”, and so does the schedule page.
Quick Start and Rovo create Jira issues only: use the wizard for service requests.
What a request contains
| Field | Notes | |—|—| | Request type | The type you picked. The request appears in the portal and the queues like any request of that type. | | Reporter | The schedule owner. RepeatWise raises the request as the owner; it is not raised on behalf of a customer. | | Summary | With variables, one line. | | Description | Sent as plain text: lists, quotes and paragraphs are kept as text; bold, links, tables and images are not. | | Priority, labels, due date | Only when the request type has the field. |
Sub-tasks, sprints and custom fields are not available for service requests, nor are an assignee, components, fix versions or a parent: the request type decides the rest (for example its default values and its automation rules).
Save checks
RepeatWise checks the request type when you save, as the schedule owner:
- Required fields RepeatWise fills (summary, description, due date, labels, priority): the wizard asks you to fill them.
- Required fields RepeatWise cannot fill (for example a custom field or an attachment) block the save: “This request type requires a field RepeatWise cannot fill: Team”. Ask a Jira Service Management administrator to make the field optional or give it a default value, or choose another request type.
- A field the request type does not have (for example labels) must be left empty.
- If the request type was removed, or the owner can no longer raise requests in the project, the save says so.
Runs, retries and the previous request
Everything else works as for issues: the run history, retries, catch-up, Run now, owner notifications, and what happens to the previous request (skip if still open, comment, or move to a status). The comment on the previous request is an internal note: customers do not see it.
A request is never raised twice
Jira Service Management cannot tell RepeatWise whether a request was already raised. So when Jira’s answer to a create is lost (Jira unavailable, timeout), RepeatWise never sends the request again. Instead it looks for it in the project, a few times over about 30 minutes (“not confirmed yet, check 1 of 3”). If it finds the request, the run continues as usual. A request with the same summary but another request type (for example one raised by hand) is never taken for it. If it does not, the run fails with:
RepeatWise sent the request at time but could not confirm it was created. Check the project; if it is not there, use Run now to create it.
The schedule then shows an error and the owner is notified. Check the service project for a request with that summary around that time; create it by hand only if it is not there, then save the schedule to resume it. Run now follows the same rule: the result stays “checking” while RepeatWise looks, then shows the same message.
Each request gets the RepeatWise recurrence issue property right after it is created, so the RepeatWise panel and JQL such as issue.property[recurrence].scheduleId = "<id>" find it like any created issue.
Permissions
The schedule owner must be able to raise requests in the service project (as an agent, or a customer of the service project) and have the Create issues permission in it. RepeatWise uses the Jira Service Management request scopes for this (read request types, create requests); see Data and privacy.