User Personas | Sprint Organizer Documentation

User Personas documentation.

Sprint Organizer supports different types of Jira users who need better
visibility into sprint activity, reporting, history, and administration.

The personas below describe common ways teams use Sprint Organizer. They
are usage profiles, not additional roles or permissions created by
the app. Access to Jira spaces, boards, sprints, and work items
continues to depend on Jira permissions.

Jira Administrator

Responsible for Jira-wide administration, visibility, and sprint
governance.

Uses Sprint Organizer to:

Monitor sprints across accessible Scrum boards and spaces
Search and filter Active, Future, Closed, and Deleted sprints
Review sprint activity through the Global Dashboard
Investigate sprint lifecycle changes in the Sprint Audit Log
Find and manage Orphan Sprints
Configure tracked boards in the Free Edition
Control how stored Sprint, Board, and Space Names are exposed
Investigate sprint-related problems across multiple teams

For Jira administrators, Sprint Organizer provides a centralized
operational view of sprint activity that would otherwise require
navigating through multiple Scrum boards.

Scrum Master / Team Lead

Responsible for day-to-day sprint execution and visibility within a
team.

Uses Sprint Organizer to:

Monitor Active and Future sprints
Identify Active sprints that have passed their planned end date
Review sprint goals and dates
Search work items using sprint properties
Review recent sprint changes
Investigate deleted sprints
Check previous sprint participation for work items
Create reusable sprint-based Jira filters and dashboards

For Scrum Masters and Team Leads, Sprint Organizer makes sprint
information easier to monitor, search, and investigate without relying
only on the board view.

Project / Delivery Manager

Responsible for coordinating delivery across teams, boards, or
spaces.

Uses Sprint Organizer to:

Monitor sprint activity across multiple teams
Compare Active and Future sprint work
Track upcoming sprint deadlines
Identify unfinished work in overdue sprints
Build cross-project sprint reports
Combine sprint metadata with status, assignee, priority, and other
Jira fields
Create sprint-aware dashboards for delivery monitoring
Review historical sprint participation

For Project and Delivery Managers, Sprint Organizer turns sprint
information into reportable Jira data that can be used across multiple
teams and spaces.

Agile Coach

Responsible for understanding and improving sprint practices across
teams.

Uses Sprint Organizer to:

Review sprint activity across multiple boards or spaces
Compare Active, Future, Closed, and Deleted sprint information
Monitor sprint creation and completion trends
Review sprint lifecycle changes
Identify unusual sprint patterns
Build reusable cross-team filters and dashboards
Analyze historical sprint participation

For Agile Coaches, Sprint Organizer provides a broader view of sprint
activity without requiring each Scrum board to be reviewed separately.

Space Administrator

Responsible for administration and visibility within one or more Jira
spaces.

Uses Sprint Organizer to:

Review sprint statistics within a space
Browse and filter sprints associated with the space
Review the Space Sprint Audit Log
Investigate sprints that are not visible in the standard sprint list
Review Orphan Sprints associated with the space
Understand sprint activity without switching between multiple board
views

Some administrative information on Space Pages is available only to Jira
administrators or Space administrators.

Sprint Organizer does not grant Space administrators additional Jira
permissions.

Standard Jira User

Works with Jira work items as part of regular team activities.

Uses Sprint Organizer primarily through Sprint Reporting fields, JQL,
saved filters, and dashboards.

Typical uses include:

Finding work items in Active or Future sprints
Searching by sprint name, state, goal, board, or dates
Finding work items that participated in previous sprints
Using saved sprint-based filters
Viewing dashboards created from Sprint Reporting data

For standard Jira users, Sprint Organizer can work mostly in the
background, making sprint information available through familiar Jira
search and reporting tools.

Permissions

The personas described above do not override Jira permissions.

Sprint Organizer:

Does not create a separate user-role model
Does not grant additional Jira privileges
Does not grant access to inaccessible spaces, boards, sprints, or
work items
Uses Jira permissions to determine what information users can
access

Administrators can optionally configure the visibility of stored Sprint,
Board, and Space Names. These settings affect the display of stored
names only and do not provide access to the underlying Jira resources.

→ See: Permissions
Settings

Persona → Features Mapping

Persona	Key Features Used	Primary Goal
Jira Administrator	Global Dashboard • Global Sprints • Orphan Sprints • Sprint Audit Log • Boards Configuration • Permissions Settings	Gain centralized sprint visibility and administer sprint-related data across Jira
Scrum Master / Team Lead	Space Dashboard • Sprints • Sprint Reporting & JQL • Dashboards & Filters • Sprint Audit Log • Deleted Sprint Tracking	Monitor sprint execution, find problems, and investigate sprint history
Project / Delivery Manager	Global Dashboard • Sprint Reporting & JQL • Dashboards & Filters • Sprint History Fields	Monitor delivery and build sprint-aware reporting across teams
Agile Coach	Global Dashboard • Global Sprints • Sprint Audit Log • Dashboards & Filters • Sprint History Fields	Analyze sprint activity and patterns across multiple teams
Space Administrator	Space Dashboard • Space Sprints • Space Orphan Sprints • Space Sprint Audit Log	Manage and investigate sprint activity within a specific Jira space
Standard Jira User	Sprint Reporting Fields • JQL • Saved Filters • Jira Dashboards	Find and understand work using sprint metadata in familiar Jira tools