Hi Atlassian community!
We’re excited to announce that we’ve officially kicked off the Early Access Program (EAP) for the modernised Jira board for company-Managed spaces. Here we’ll cover off the upcoming changes to the board experience and how you can sign-up for early access.
We're keen to invite 2-3 customers in the EAP and this is your chance to get early access to powerful new features and directly influence how the board view evolves in Jira.
We’ll also make this available via Jira Labs once the EAP concludes.
If you’ve been following our journey, the modernised board went GA to team-managed software boards in July (read our community post here) allowing us to unify 3 different board experiences, down to 2.
Now we’ve got our sights on unifying boards in company-managed spaces.
Please note: that for now we're only targeting boards that are scoped to Simple boards (see more below under known gaps/caveats)
| Feature | How it works |
|---|---|
|
Board layout and navigation |
Preview: |
|
Improved filtering and grouping experience |
Filtering
Note: Quick filters (admin defined/saved) filters remain unchanged but renamed to Custom filters Grouping
Preview: |
|
Save your board configuration |
Preview: |
|
Subtask summaries |
Preview: Note: this feature is experimental and may change or evolve as the EAP progresses |
|
Column limits |
Preview: |
|
Column layout |
Preview: |
|
Column configuration (admin only) |
Preview: |
More than just a feature update, this is a completely overhauled board experience. We’ve made thousands of under-the-hood improvements to performance, design, and usability.
We need teams who:
As an early access this product is actively evolving — some features are still being refined, and you may notice changes to designs or functionality along the way.
| Feature | Description | Our plan |
|---|---|---|
|
Limited to single-space boards (i.e. simple boards) |
Admins can use board filters to include work items from multiple spaces. Multi-space company-managed boards aren’t included in this program. |
In the event the board’s scope is changed to reference more than one space, board will automatically revert back to the classic board. Multi-space (including global boards) is on our roadmap. |
|
Add/create release from Board (Kanban) |
Unique to company-managed Kanban boards — admins could create/select releases based on completed/shipped work items. |
Not supported This feature has extremely low adoption/usage and not supported during the EAP and will likely be sunset on release. |
|
Bulk select/change cards |
Multiple cards (only in the same column) could be selected and transitioned on the board. |
In development This feature is currently being redesigned and on the roadmap to be brought back however not be available during the EAP. |
We'll give you heads-up for any major changes and support you through transitions.
We're selecting just 2-3 customers for this cohort, so spots are limited! I will hold an introductory call to discuss future details.
To express interest:
We'll review all expressions of interest and confirm participation by next week (26 Aug, 2026) with next steps and exact dates.
Can I opt-out of the new experience if so, how?
Yes, throughout the duration of the EAP program, users will be able to opt-out of the new experience.
What happens after the EAP ends?
Once the EAP concludes, your boards will revert back to the classic Jira board.
However, once we start rolling out to production, we will open this experience up to Jira Labs (beta).
Is it possible to opt-in early or get access after the EAP?
Yes - both EAP and non-EAP customers will be able to enable the new board experience once the product officially starts rolling out via Jira Labs toggle. This will occur shortly after the EAP concludes.
Please note: to enable this feature in Jira Labs you must be an organisation admin.
How can teams leave feedback?
Teams can share proactive feedback during the EAP using the in-product feedback button located in the top-right section of the board. This will get sent directly to our team for review.
Peter Oh
6 comments