What is changing?
Connect apps can take advantage of the general pages module in order to contribute an iframe that consumes an entire Jira page aside from template artifacts such as navigation, footer, etc. For improved user experience, we are introducing general pages into Jira’s single page application (SPA) shell. This means users will be able to navigate between SPA locations which will soon include general pages.
Most apps will not need to be modified to accommodate these changes, however, the changes are complex and there is a risk of impacting some apps.
Why is this changing?
This feature will improve the perceived and actual performance of navigating to general pages. It is part of our initiative to improve user experience. During our testing phase we were able to improve the time to interactive (TTI) by almost 1 second.
When will this change take effect?
It is critical for us to coordinate the release process with our Ecosystem partners to mitigate this risk. Previous soaking on app developer testing tenants has taken place a few times already - General pages in SPA and Connect in SPA invitation.
We plan to gradually release the SPA general pages feature to customers starting on May 18, 2020. The rollout will occur on a tenant by tenant basis which means that during the rollout, apps will see both the new and old behaviours.
Testing your app
- Enrol a test tenant into the Cloud Vendor First Release Group by visiting http://go.atlassian.com/cloud-vendor-first-jira-form.
- Install your app in the test tenant and test all features relating to general pages.
- If you see any anomalies, please make changes to the app, ensuring they work for non-SPA and SPA behaviours.
- Please share any learnings about changes you had to make with the developer community.