Permissions Explained | Sprint Organizer Documentation

Permissions Explained documentation.

Overview

Sprint Organizer is built on Jira's native permission model and does not introduce its own access control system.

By default, the application respects permissions assigned within Jira and limits the information displayed based on the resources the current user is authorized to access.

For this reason, all settings that may expose additional Project, Board, or Sprint names are disabled by default.

Administrators can explicitly enable selected permission overrides in Sprint Organizer. These settings allow stored names to be displayed in specific application views or Sprint Reporting custom fields even when the corresponding resource is private, deleted, or inaccessible to the current user.

Permission overrides affect only the visibility of stored names. They do not grant access to the underlying Jira project, board, sprint, or issue.

To learn more about available overrides and their scope, see Permissions Settings.

Permission Model

Sprint Organizer determines data visibility using existing Jira permissions.

When displaying sprint information, the application considers whether the current user has access to:

If access to a resource is restricted, Sprint Organizer limits the information presented accordingly.

No additional permission configuration is required after installation. By default, all permission override settings are disabled.

Administrators can optionally enable selected overrides from Permissions Settings.

Global Administration Pages

Global Administration pages aggregate sprint information across the Jira instance.

By default, project and board information displayed on these pages follows the current user's Jira permissions.

This applies to pages such as:

Administrators can enable separate permission overrides for Project Names and Board Names on administration pages.

When enabled, Sprint Organizer may display previously stored names for projects or boards that are private, deleted, or otherwise inaccessible to the current user.

These overrides expose only the stored names and do not provide access to the underlying Jira resources.

See Permissions Settings for configuration details.

Project Pages

Project Pages display sprint information related to the current Jira project.

Sprint Organizer limits the displayed data to the context of that project while continuing to use Jira permissions for access to underlying resources.

By default, board names that are not available to the current user are not exposed.

A separate Project Page permission override can be enabled to allow Sprint Organizer to display previously stored Board Names on project pages, including names of boards that are private, deleted, or otherwise inaccessible.

This setting is independent from the Board Name override used on Global Administration pages.

Enabling the override does not grant access to the board itself or to resources outside the current project.

See Permissions Settings for configuration details.

Board Visibility

Sprint Organizer uses Jira permissions when retrieving current board information.

If a board is inaccessible to the current user or has been deleted, current information about that board may no longer be available through Jira.

When the appropriate permission override is enabled, Sprint Organizer can use previously stored metadata to display the Board Name even when the board itself is no longer accessible.

This does not restore the board or grant the user permission to access it.

Stored names are available only if Sprint Organizer previously collected them. Boards that became unavailable before Sprint Organizer was installed may therefore be displayed without a name.

Issue Visibility

Sprint Reporting custom fields are available only on issues the user is permitted to view.

Even when sprint information exists in Sprint Organizer, users cannot access issue-level information unless they have permission to view the corresponding Jira issue.

By default, Sprint and Board Names are not stored in Sprint Reporting custom fields.

Administrators can explicitly enable storing these names from Custom Fields Settings. Because text-based custom fields cannot dynamically hide individual values based on the permissions of the user viewing an issue, enabling these settings may expose stored Sprint or Board Names to users who can access the issue.

Enabling names in custom fields does not grant access to the corresponding sprint or board.

For more information, see Permissions Settings.

Deleted Sprint Tracking

Deleted sprint information is based on metadata previously collected by Sprint Organizer.

By default, names associated with deleted or inaccessible resources are displayed according to Jira permissions.

When the appropriate permission overrides are enabled, Sprint Organizer may display previously stored Project Names and Board Names associated with deleted sprints even when those resources are no longer accessible through Jira.

Permission overrides do not provide access to the deleted resource or any inaccessible Jira content. They only control whether previously stored names can be displayed.

Names can only be shown if they were known to Sprint Organizer before the corresponding resource became unavailable.

Orphan Sprints

Orphan sprints may be associated with boards that have been deleted and are therefore no longer available through Jira.

By default, Sprint Organizer does not expose stored names when Jira permissions do not allow them to be retrieved.

When the corresponding permission override is enabled, previously stored Board or Project Names can be displayed where available.

Because this information must have been collected beforehand, names of boards or projects that became unavailable before Sprint Organizer was installed may not be available.

Permission overrides do not provide access to the original board, project, or its content.

Administrative Access

Installing Sprint Organizer does not grant additional Jira administrative privileges.

Application administrators continue to use Jira's existing administrative permissions to configure and manage the application.

Sprint Organizer does not maintain a separate administrator role.

Permission override settings control the visibility of selected stored names but do not modify Jira permissions or grant additional access to Jira resources.

Limitations

The following permission-related limitations apply:

Related Pages