Use Data Center EAP product versions in testing environments
This Early Access Program (EAP) provides admins with an opportunity to explore new service account features before they reach General Availability (GA). Testing these versions in controlled environments helps ensure compatibility, readiness, and smoother rollouts.
1. Prepare a testing environment
To effectively trial the EAP versions:
Use a dedicated non-production environment: Mirror your production setup as closely as possible (infrastructure, integrations, and scale).
Isolate test instances: Ensure your testing instance has no access to production data or external systems (unless intentionally part of the test).
Snapshot and backup: Before upgrading to an EAP, create a snapshot or backup of the environment to enable quick rollback.
2. Install the EAP version
These EAP builds are designed for evaluation and feedback, not for production deployment. They include new features, performance optimisations, and fixes still under validation.
Download the EAP build:
EAP for Jira 11.1
EAP for Confluence 10.1Review the release notes to understand what has changed, what’s experimental, and any known issues.
Upgrade your test instance:
Shut down your test cluster/node(s).
Apply the EAP build following the same upgrade procedure as a production upgrade.
Start the instance and validate the upgrade.
3. Test service account functionalities
Focus your testing on:
New features: Validate new capabilities available in service accounts against your use cases.
Integrations: Confirm that apps, plugins, and external connectors function correctly.
Performance: Run load or scalability tests if possible to ensure no regressions.
We recommend documenting your test plans so you can reuse them for future EAP or GA upgrades.
4. Give feedback
We encourage you to share feedback on service accounts during the EAP:
You can report issues and bugs, and give feedback through our JSM Portal.
This feedback loop helps us improve our service accounts feature for the final GA release.
EAP best practices
Never run EAP builds in production.
Note all changes tested and outcomes.
Engage stakeholders early by showcasing new features in sandbox environments.
Use EAP learnings to prepare upgrade guides for your production rollout.
