Roles can be assigned as reminder recipients exclusively through Jira Automation rules. This ensures that automated nudges reach all current members of a space role without manual user assignment.
Visibility & Permissions
Who can see space role names depends on their Jira permissions:
|
Permissions |
Display Name in UI |
Details |
|---|---|---|
|
Space Admin / Jira Admin |
Actual role name (e.g., Developers) |
The app provides role names for spaces where the user holds administrative permissions. |
|
Standard User |
|
Project roles are hidden for users without admin permissions. |
Once a role is removed from a space, the app can no longer resolve its identity. It will appear as Unknown Project Role for all users, regardless of administrative permissions.
|
Role |
Display name in UI |
Details |
|---|---|---|
|
Deleted / Invalid Role |
|
Displayed when a role assigned via Automation no longer exists in the space. |
Where does this apply?
Role privacy rules apply everywhere across the app interface, including the context panel, the main reminder grid, and the reminder’s details.
Editing Reminders with Space Roles
When editing a reminder that was created by a Jira Automation rule containing Space roles:
-
For Standard Users:
Space role recipients appear as locked (without a remove
Xicon) and cannot be modified or added. Saving edits will retain all existing Space roles intact. -
For Space / Jira Administrators:
Administrators cannot add new Space roles via the manual UI form. However, they can remove existing roles from the reminder or restore a removed role back to the Recipients field before saving changes.
Why can't I manually select a Space Role when creating a reminder?
Jira restricts Space Role data queries to administrators. To prevent permission conflicts and broken notifications, role-based recipient assignment is managed exclusively via Jira Automation triggers.