Major release updates for Data Center

Jira Development Jira Data Center
, , , , ,
1

Hi Community :waving_hand: ,

We’re sharing a concise one‑pager (five-pager :wink:) that pulls together the planned major release updates for Data Center. It’s your primary reference for key themes, likely areas of impact, and what may require attention from app vendors and technical teams.

Action: Review the document and share it with your engineering, product, and release stakeholders if the outlined changes impact your roadmap, compatibility plans, or customer support readiness.

See also: Confluence 11.0 release EAP available now for Confluence-specific updates and feedback. Head there for product-specific discussion. :speech_balloon:

Thanks for taking a look—please drop questions or feedback in the thread.

The Data Center team
Major release updates for Data Center.pdf (17.9 KB)

2

The five-pager is missing app-specific changes like the complete Bandana removal or methods that are removed from the Confluence PageManager (at least getPageIds and countCurrentBlogs), which may increase the impact massively.

3

+ removing access to *DAO classes (Confuence) - no equivalent for getBlogPostByTitle

4

@cheinig
Thanks for providing feedback, we will get back to you on countCurrentBlogs and others.
Please see this link for getPageIDs.

5

@adam.labus

You can find an equivalent REST API your app for these requirements.

For example: getBlogPostByTitle can be translated to:
{{baseUrl}}/rest/api/content?type=blogpost&spaceKey={{spaceKey}}&title={{blogTitle}}&expand=version,space,history

You can find the REST API at DAC here: https://developer.atlassian.com/server/confluence/rest/

Please let me know if you have further questions.

6

@cheinig
You can find an equivalent REST API your app for these requirements.

For example: countCurrentBlogs can be translated to totalSize in:
{{baseUrl}}/rest/api/content/search?cql=type=blogpost&status=current&limit=1

You can also add more filters like: space="{{spaceKey}}"

Please let me know if you further questions

7

In the item JNDI sanitization and OSWorkflow changes there is mention of removing com.opensymphony.workflow.loader and others opensymphony packages. Is there an alternative?

8

This is going to depend on what features of OpenSymphony you were using. Is there something specific you are worried about here? In general the removals are components that were not used within the products.

9

We are using it for workflows, for example running business logic on Issue transition. We are using JiraWorkflow with the WorkflowManager which give us ActionDescriptor and WorkflowDescriptor. We are also using ValidatorDescriptor and AbstractDescriptor, from com.opensymphony.workflow.loader .

10

Thanks! I do not think these components are removed. I’ll look into this, it is possible this package was either partly-removed or was included in the listing in error.

11

Hi again, I’ve confirmed this is an error in the release notes here. com.opensymphony.workflow.loader is not removed or slated for removal. In addition the com.opensymphony.workflow.util package is only removing classes related to other features that were removed, and most of it is still present. We will work to correct these notes.

12

That’s great new thank you! By the way, are these warnings logs incorrect then ?

[c.a.p.o.hook.dmz.DmzResolverHook] Package com.opensymphony.module.propertyset is deprecated and will be made unavailable for export to plugin in a future release
[c.a.p.o.hook.dmz.DmzResolverHook] Package com.opensymphony.workflow is deprecated and will be made unavailable for export to plugin in a future release
[c.a.p.o.hook.dmz.DmzResolverHook] Package com.opensymphony.workflow.loader is deprecated and will be made unavailable for export to plugin in a future release

13

I checked and these deprecation warnings are not new. We do discourage using the OpenSymphony libraries unless you have to, but we do not plan to remove or unexport them. Apologies for the confusion the messages are causing.