Fearless Scrum Board for Jira
Installation and access
Private pilot · Public Marketplace release not yet approved. Public Marketplace approval is not complete. These instructions describe the current production UI, version 2.10.0.
Join an existing pilot site
Ask your Jira administrator whether Fearless Scrum Board for Jira is already installed on your site. Sign in with your own Atlassian account, obtain access to the agreed Jira project, and open Fearless Scrum Board in that project's navigation. Installing the app does not grant project access or extra Jira permissions.
Select Refresh and check the displayed project and Sprint before editing.
Installation when approved
Public installation is not available yet. Contact jimi@fearlessagility.com about a controlled pilot. Do not use an old developer-console installation link or assume that a private Marketplace token grants access.
Once an installation route is approved for your site, an authorized Jira site administrator should use the approved listing or installation route, select the intended site, review the requested permissions and confirm installation. Then open the app from the agreed project's navigation and verify the project and Sprint with Refresh. No private installation link is provided here.
The current private pilot is free and unlicensed. Public pricing and release timing have not been decided. Contact us for the installation route appropriate to your site.
Project prerequisites
The project must resolve to exactly one accessible, eligible Sprint-capable board. Discovery supports Scrum boards and team-managed boards reported by Jira as simple when their Sprint API is accessible. A failed permission or Sprint check does not count as a valid configuration. This is not a Kanban workflow.
One active Sprint takes precedence over future Sprints. Multiple active Sprints are ambiguous. With no active Sprint, exactly one future Sprint is required. The app does not choose between several future Sprints by date or name, or create one for you.
Ask your administrator to review ambiguous board or Sprint configuration. Do not delete a board or Sprint merely to dismiss an error.
What you can see and change
The app checks Browse Projects permission. Jira permissions, board filters, project scope and issue security govern Jira-backed work. The Product Backlog shows visible, unassigned, incomplete work; it is not a complete list of every issue on your site. Work already in another active or future Sprint is excluded from that backlog.
Project administrators have additional app-data export and erasure controls. These controls are not a prerequisite for ordinary planning.
App permissions and Jira permissions
The app requests Forge storage access for shared app records; read access for Jira projects, boards, issue details, JQL and Sprints; write access for Sprint Goals and Sprint membership; and issue-deletion access for Trim the Tail. Jira calls run as the current user. App authorization does not override that user's Jira permissions, board filters or issue security.
Ordinary access requires Browse Projects. App-data export and erasure additionally require Administer Projects. Jira-backed changes require the applicable Jira permissions; Browse Projects alone does not grant permission to change Sprint membership, update a Sprint Goal or delete issues. Shared app tasks are not Jira subtasks.
Warning: Trim the Tail permanently deletes selected underlying Jira issues. It is not archiving. Administrator app-data erasure is separate and permanently seals the selected scope against future writes; it is not a reset. Read the user guide before using either control.
Read our privacy page. For product help, email jimi@fearlessagility.com.