Permissions Settings | Sprint Organizer Documentation

Permissions Settings documentation.

Sprint Organizer provides permission settings that control whether Sprint Names, Board Names, and Project Names can be stored or displayed by the application.

By default, Sprint Organizer follows Jira permissions and avoids exposing names of resources that a user may not be authorized to access. For this reason, all permission override and name storage settings are disabled by default and must be explicitly enabled by an administrator when required.

Permission settings are divided into:

Image{.img-center .img-large}

Custom Fields Settings

Custom Fields Settings control whether sprint and board names are stored directly in Sprint Reporting custom fields.

Available settings:

By default, names are not stored because Jira text-based custom fields cannot dynamically restrict individual values based on the permissions of the user viewing them.

Enabling these settings allows names to be stored in the corresponding custom fields, including names of resources that may be private, inaccessible, or deleted.

This makes the names available anywhere these custom fields are used, including:

Updating Custom Fields

Changes to Custom Fields Settings are not applied immediately to existing issues.

After changing a setting, select Update custom fields to start updating the Sprint Reporting fields on existing issues.

The update runs in the background and may take some time depending on the number of affected issues.

You do not need to keep the Permissions page or Sprint Organizer open while the update is running. You can safely navigate away, close the page, or close the application. The update will continue in the background.

Until the update is complete, some issues may temporarily contain values based on the previous configuration.

Image{.img-center .img-large}

Administration Page Settings

Administration Page Settings control how project and board names are displayed within Sprint Organizer's Jira administration pages.

Available settings:

When an override is disabled, Sprint Organizer follows the current user's Jira permissions when displaying names.

When enabled, Sprint Organizer can use stored metadata to display names even when the corresponding project or board is not accessible to the current user through Jira.

This may include names of private, inaccessible, or deleted projects and boards.

Changes to Administration Page Settings take effect immediately because these settings control data displayed directly by Sprint Organizer.

Project Page Settings

Project Page Settings control how board names are displayed on Sprint Organizer pages available within individual Jira projects.

Available setting:

When disabled, board names are displayed according to the current user's Jira permissions.

When enabled, Sprint Organizer can use stored board metadata to display names that would otherwise be unavailable, including names of private, inaccessible, or deleted boards.

Changes to Project Page Settings take effect immediately because these settings control data displayed directly by Sprint Organizer.

Permission Override Considerations

Permission overrides should be enabled only when displaying stored resource names is appropriate for users who have access to the corresponding Sprint Organizer pages.

Enabling an override does not grant access to the underlying Jira project, board, sprint, or issue. It only allows Sprint Organizer to display names stored by the application.

Similarly, enabling names in Sprint Reporting custom fields does not change Jira permissions. However, because those names are stored as custom field values, they may be visible to users who can access the corresponding issues and fields.

Applying Changes

Administration Page Settings and Project Page Settings take effect immediately.

Changes to Custom Fields Settings require an additional update:

  1. Change the required Custom Fields Settings.
  2. Select Update custom fields.
  3. Sprint Organizer starts updating affected issues in the background.
  4. You can safely leave the page or close Sprint Organizer while the update is running.
  5. The new configuration is applied progressively until all affected issues have been processed.

The time required depends on the number of issues that need to be updated.

Related Pages