Skip to content

Creating Out of Office Rules for JSM Customers

Service management customers - the people who raise requests in the customer portal - can have out of office rules of their own. An administrator switches the feature on for the whole site, then creates and manages each customer's rules inside the app.

Choose which customers can have out of office rules

The feature is off until someone turns it on. Administration is open to Jira administrators only.

  1. Open Out of Office Assistant from Apps in the Jira sidebar.

  2. Go to Administration > General Settings.

  3. Under Service Management > Customers, tick Portal-only customers, Members of these groups, or both. For Members of these groups, add at least one group in the field below it.

General Settings has no Save button. The change applies the moment you tick the box. Sites that used the earlier Allow customers to have out of office rules checkbox start with Portal-only customers ticked. If you untick both options, the settings show Select at least one option so that out of office rules can be created for customers., the Customers view disappears and no new rule can be created for a customer. Existing customer rules are kept. While both options are off, they start no new approval handovers; handovers already made are still reversed when the rule ends.

settings-general-administration.webp
The Service Management group in Administration > General Settings.

The space picker directly above the checkbox is a different setting - it controls which service spaces show an agent's out of office status to customers. See Agent Availability Display in JSM Customer Portal.

What a customer can and cannot do

A customer holds no Jira licence and the portal has no equivalent screen, so the app itself is out of reach.

Task

Service management customer

Licensed Jira user

Open the Out of Office Assistant app

No

Yes, from Apps in the sidebar

Create and edit their own rules

No. An administrator does it for them

Yes, on My Rules

Have an out of office rule at all

Only when the setting above includes them

Always

See who is out of office

Only the agent assigned to a request they can see, in the portal

Team Availability, for people they share a space with. Jira admins and Out of Office admins see everyone

The portal discloses only the assigned agent's name, an OUT OF OFFICE lozenge and the absence period. The message written on a rule stays internal to agents unless that rule has Share this message with service desk customers. ticked - see Service Desk Customer Notifications.

Create a rule for a customer

  1. Open the Team Availability tab.

  2. Above the table, click Customers. The table lists the customers chosen in the settings, with a search box and the page size but no space, availability or integration filters.

  3. Find the person and click Show details.

  4. On the Rules tab, select Add rule for this user. Until the person has a rule the tab reads No rules yet and that button sits beside Reload.

  5. Fill in the form. It opens under Rule for: and the person's name, headed Schedule their Out of Office Rule, with the same fields as your own rules. Rule Configuration Guide describes each one.

  6. Click Create Rule.

Create Rule stays disabled until the rule actually does something. Dates alone are not enough: name a coverer, name an approver coverer, write a message, or tick the glance-only box. An approver coverer takes the customer's place in the chosen approval field of open requests within about an hour after the absence starts. Within about an hour after it ends, the customer is put back. Deleting the rule or changing its approver coverer puts the customer back within seconds; a newly named approver coverer follows with the app's next periodic run. Nobody has to edit the request for this to happen.

Customers lists portal-only customer accounts, members of the chosen groups who hold no Jira licence, or both, depending on the settings. Someone who holds a Jira licence stays under Users, even when they are in a chosen group. Group members are matched against the global integrations like any other user; portal-only customers are not. The search box finds customers whose name or email address has a word that starts with what you type: smi finds John Smith, mith does not. If a page reads No matches on this page yet. The list continues on the next page., open the next page. If a search matches too many accounts, the list reads Too many matches to check them all. Please narrow your search. If the customer list reads No users found. and you expected to see somebody, switch back to Users and search there.