Permissions | Sprint Organizer Documentation

Permissions documentation.

Overview

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

The application respects the permissions assigned within Jira, ensuring that users only see sprint information for projects and boards they are authorized to access. Sprint Organizer never bypasses, extends, or overrides Jira security.

This approach provides a consistent user experience while maintaining the same level of data protection as the underlying Jira platform.

Permission Model

Sprint Organizer determines data visibility using existing Jira permissions.

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

If access to any of these resources is restricted, Sprint Organizer limits the information presented accordingly.

No additional permission configuration is required after installation.

Global Administration Pages

Global Administration pages aggregate sprint information across the Jira instance.

Although these pages display data from multiple projects and boards, users only see information for resources they are permitted to access.

This applies to:

The application never exposes sprint information from inaccessible projects or boards.

Project Pages

Project Pages display information related to the current project.

Sprint Organizer automatically limits the displayed data to sprint boards associated with that project while continuing to respect Jira's existing permission model.

Users cannot use Project Pages to view information belonging to other projects unless they already have permission within Jira.

Board Visibility

Sprint information is only available when the user has access to the board that owns the sprint.

If a board becomes unavailable because of permission changes or deletion, Sprint Organizer no longer displays its sprint information.

Historical audit entries associated with inaccessible boards are also hidden.

Issue Visibility

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

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

This behavior ensures complete consistency with Jira's security model.

Deleted Sprint Tracking

Deleted sprint information follows the same permission rules as active sprint data.

Users can only view deleted sprints that belong to projects and boards they are authorized to access.

Deleted sprint tracking does not provide access to historical information from inaccessible projects.

Administrative Access

Installing Sprint Organizer does not grant additional 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.

Limitations

Sprint Organizer cannot display sprint information that is unavailable through Jira permissions.

If access to a project, board, or issue is revoked, the corresponding sprint information is no longer visible within the application.

Permission changes made in Jira are reflected automatically after Sprint Organizer synchronizes its data.

Related Pages