Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Project restrictions

In-project menu

If you are unable to see ‘Release planning & reports’ menu in a software project’s left navigation check the Project restrictions configurations explained below.

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 the instance level setting screen as explained in Navigating to Release planning & reports app in Jira. Here, under the App settings tab - project level restrictions can be configured.

Default available

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 in the exception list.

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

Default unavailable

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 in 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 meta data to versions or releases in Jira. This meta data 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.

Project level custom fields can be configured from the in-project screen as explained in

Global default fields

These are the fields that will always apply to versions/releases across all projects. Right now, there is only one global default field which stores the information about where the version was created - from Jira or from within the app!

Global custom fields

These are the fields that will be available to versions/releases across all projects. Currently, following types of fields are supported

  • Single line

  • Multi line

  • Single select

  • Multi select

  • Date

  • Single select user

Each of the fields have name, type & details.

At the time of installation, following 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)

Edit & Delete

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

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.

  • No labels