Restricting Out of Office to Specific Spaces
Out of Office Assistant can be confined to specific spaces in four ways, and they are not interchangeable. This page covers delegated administration and the data security policy in full, and points you to the other two. Jira now calls projects spaces, and both Jira and the app use that wording.
Choose the right restriction
What you want to limit | Where you set it |
|---|---|
Which work items one rule reassigns or comments on | The rule's own Work Item Selection field, set to Spaces or JQL Work Item Filter. See Rule Configuration Guide |
Which spaces a delegated administrator may manage rules in | App Settings > Permissions > Space Admins, below |
Whether a space's customer portal shows agent absence | App Settings > General Settings > Service Management, the picker Display agent out of office status in the Customer Portal. See Agent Availability Display in JSM Customer Portal |
Whether the app operates in a space at all | Your organization's data security policy, below |
Scoping a rule decides which work items are acted on, not who counts as absent: a rule limited to one space still shows that person as out of office everywhere in Jira.
Delegate rule administration to specific spaces
A Space Admin manages Out of Office rules on behalf of other people, but only for members of the spaces you name. Granting it takes two steps, one in Jira and one in the app.
In Jira, open the space, go to Space settings > Access, and give the person space admin rights there. Being the Space Owner does not grant them.
In Out of Office Assistant, open App Settings > Permissions and add that space to the Space Admins selection. Repeat for every space the person should administer.
Neither step implies the other. Someone listed under Space Admins who is not a space admin in the space's own Space settings > Access gains no Out of Office rights there, and a Jira space admin whose space is not selected in App Settings gains none either.
With both in place, that person can create and change Out of Office rules and personal templates only for members of those spaces. Out of Office Admins and Jira admins are not narrowed by this selection - they manage every user. The full role model is on Permissions and Access Requirements.
Delegation always names spaces
There is no option to delegate all spaces at once; the earlier all-projects setting no longer exists. A space that is not selected is not delegated, and spaces created later are never picked up automatically, so add them to the selection as you go.
Upgraded from the Connect version? The old all-projects setting has no equivalent here, so the app asks you in App Settings to select your spaces again. Delegated administration stays inactive until you do. See Migrating from Connect to Forge.
Switch the app off in specific spaces
Delegation decides who administers rules. To stop the app operating in a space at all, block its access to that space in your organization's data security policy at admin.atlassian.com. The app then loses read and write access to the work items in that space, so nothing there is reassigned or commented on, including by rules that were already running.
That control belongs to Atlassian, not to this app, and Atlassian changes its screens, so follow the current steps in Block Marketplace and custom app access rather than a copy. Blocking needs organization administrator rights, which Jira administrator rights do not include, and restricting one named app to selected spaces needs Atlassian Guard Standard or Premium - without that subscription a policy can only block all eligible apps at once.
To confirm the block took effect, assign a work item in a blocked space to someone with an active rule: it stays with them, while the same test in an unblocked space still hands the work item to their coverer.