Project restrictions

App settings

There could be projects in Jira where you don’t need to use Release planning & reports app. Or there could be only a handful of projects, that need to use the app. Either way, the Jira admin can ensure the requirements are met using project restrictions setting.

As a Jira admin, navigate to Jira Apps settings >> Configuration section of Release Planning & Reports >> App settings tab.

Read more Navigating to Release planning & reports app in Jira | Jira admin facing screen.

Default available

Open

When the configuration is similar to above, that means - Release planning & reports menu is available on all projects by default. Except for projects that are added to the exception list.

e.g. in the above example, Release planning & reports menu will be available in all projects except ‘UpRaise Apps’.

Default unavailable

Open

When the configuration is similar to above, that means - Release planning & reports menu is not available on any projects by default. Except for projects that are added to the exception list.

e.g. in the above example, Release planning & reports menu will not be available in any project except ‘UpRaise Apps’.

Global fields

Release planning & reports app adds the capability of adding metadata to versions or releases in Jira. This metadata can be broadly considered into two buckets - Global & Project level.

As the names suggest, Global fields are available across all the projects on that Jira instance & Project level fields are available only within the Jira projects they are defined in.

Global default fields

These are the fields that will always apply to Versions, Releases & filters on the Releases page across all projects. Right now, there is only one global default field that stores the information about where the version was created - from Jira or from within the app!

Global custom fields

Below listed are the field types available currently that are available to create Global custom field to be used across all projects.

• Single line

• Multi line

• Single-select

• Multi-select

• Date

• Single select user

Each of the fields has a name, type & details.

At the time of installation, the following Global custom fields are made available

• Release type - Single select (Feature release, Patch release)

• Release owner - Single select user

• Impacted areas - Multi-select (Backend, Frontend, Integration points, Performance)

• Release status - Single select (Draft, Pending approval, Approved, In progress, On hold, Live)

Add

New custom fields can be added by clicking on the ‘Add custom field’ button available on the Global custom fields table. Once clicked, this is how the form shows up.

Edit & Delete

Listed custom fields can be edited or deleted from the small arrow icon on the right-hand side.