To define the ARNR access and permissions, as Jira admin, you need to manage settings at the app level that allows users to access ARNR app within Jira and the project. Another setting you need to manage is at Jira project level where you can define who should manage ARNR Templates and Rules.

Jira project-level permissions

There are two types of Jira projects in Jira, based on that you can refer the relevant navigations explained below -

For company-managed project

• Navigate to the Project settings in the left navigation under the relevant project

• Navigate to Permissions in the left navigation again

• Click on Actions in the right top corner >> Click on Edit permissions

• Go to Manage Automated Release Notes & Reports section >> Click on Update

Open

This project level setting will decide who will have the access to ARNR menu. For eg. If a user does not have proper permission at Jira project level, in that case having access at the app level (explained below) will not allow them to access ARNR menu in cross-project or in-project navigation.

As you can see in above image, you can grant access based on project roles, application access, group, etc. Based on these settings users will have access to ARNR templates and rules.

For Team managed projects

Ensure that the relevant project role has app permission to use & update ARNR. You can navigate to permissions settings using these steps -

• Go to relevant team-managed Jira project

• Navigate to Project settings option from the left navigation pane

• Click on the Access menu

• Click on Manage Roles button

• Select relevant role/s

• Go to App Permissions tab

• Enable permissions specific to Automated release notes and reports

App level access and permission settings

As Jira admin, navigate to Manage apps >> Automated Release Notes and Reports Configurations >> App settings tab

Cross - Project screen permission

On App setting tab there are two sections. In the first section called Access ARNR cross-project screen, you can decide whether the cross-project screen will be enabled for all users or users from selected Jira group/s.

Open

Cross project screen ARNR app navigation

As the name suggests, the Cross-Project screen means that one can access ARNR from the Apps option that is available in the Jira top menu.

In project screen permission

The second section has multiple settings, as shown in the images below. For each type of permission, you can enable or disable access for users from all projects or selected projects.

This setting allows you to define whether the in-project screen will be enabled or disabled for users from all/selected projects.

In project screen ARNR app navigation

In project screen means the ARN screen will be visible from the respective project’s left navigation if the user has the relevant permissions we discussed above.

Permissions for granular control

These permissions under the app settings tab give Jira admins more control over sensitive features of ARNR to protect the organization's data from being released in the public domain.

• Access ARNR in-project screen - If the ARNR app is utilized across multiple projects, then this setting allows to decide for what all projects ARNR’s in project screen (ARNR in project’s menu) are displayed

• Create new template - If the ARNR app is utilized across multiple projects, then it becomes important to contain the template creation capabilities. e.g. to ensure compliance with corporate branding etc

  • That can be configured via the template creation permission. This setting is available only to the Jira admins.

• Send email to external email ID - Jira admin can disable saving of external addresses within email rule action to prevent release notes emails from being sent outside the organization.

• Push announcement to JSM portal - Jira admin can disable publishing release notes to external endpoints through post-action to prevent release notes from being sent to an external endpoint.

• Post release notes to external endpoints - With this permission define for which all projects, Actions | POST to external endpoint pre defined url (HTML, JSON, Markdown, Slack) action should be available.

• Publish release notes to Linkedin - This permission is to define for what all projects Actions | Publish to social media action should be available.

• Publish release notes to release pages & widgets - Release pages & Widgets can be potentially misconfigured to publish data that is not supposed to be published. This permission ensures that Jira admins can control which projects have this feature enabled and which don’t.

• Allow release notes generation through AI - This permission ensures that Jira admins can control which projects have this feature enabled and which don’t.