Warning: Application Updates allowing upgrades to 10.4.1

[David Yu]

Marketplace may have mis-tagged version compatibility all wrong on JSW and JSM updates. It's allowing my 9.12.X version to update to 10.4.1. Even if you are on 10.3.X LTS, it'll push you to 10.4.1.

Going to have a really bad day if you click on Update.

Edit: to clarify, I only tested the Update on 10.3.4, and the fault might just be in 10.3.4 build. Here's how the screen looks upgrading from 10.3.3 -> 10.3.4. It thinks I have Jira Core 10.4.1 which I clearly don't.

For those doing upgrades to 10.3.X, you can fetch the proper versions here:

https://marketplace.atlassian.com/apps/1213607/jira-software/version-history

https://marketplace.atlassian.com/apps/1213632/jira-service-management/version-history

[Thiago Masutti · Accepted solution]

Hi.

I'm Thiago Masutti and I'm a Premier Support Engineer at Atlassian.

Thanks for reporting this issue.

We were able to identify the root cause as a bug on one of the Marketplace REST API and the issue is now resolved.

Some additional details can be found on JRASERVER-78671 .

I appreciate your patience and partnership on working with us.

Kind regards,
Thiago Masutti
Premier Support Engineer | Atlassian

[Trudy Claspill]

Hello @David Yu 

What exactly are you trying to point out as a problem?

The version numbering for Jira Service Management does indeed jump from 5.x.x directly to 10.x.x.

https://confluence.atlassian.com/servicemanagement/jira-service-management-10-0-x-release-notes-1387597537.html

The 5.x.x versions aligned with the 9.x.x versioning of Jira Software. With the release of Jira Software 10.x.x the version numbering on JSM was shifted to be the same.

[David Yu]

Look closely again. It's pushing out a 10.4.1 (the latest bleeding edge version) on a 9.12.X LTS Jira install. They are not supposed to be marked compatible.

[Trudy Claspill]

I must be missing something. Where are you getting the information about incompatibility? 

Are you talking about incompatibility between upgrading JSM to 10.4.1 while leaving Jira Software at 9.12.x on the same instance?

In the documentation concerning upgrades it does say that if you have both Jira and JSM on the same instance, Jira should be upgraded first. I have not done a DC upgrade for a long time so I do not know if clicking on the Upgrade link under JSM first instead will result in the system recognizing that Jira is also on the instance, halt the upgrade process, and force you to upgrade Jira first.

[David Bakkers]

You've got it right.

If you click the 'Upgrade' button, the process will start, then tell you that you need to upgrade the Jira core to v10 first before being able to do the v10 JSM upgrade, then it won't progress any further.

[David Yu]

I'm repairing my test 10.3.4 instance right now because the JSW upgrade button moved me to 10.4.1, instead of 10.3.4.

Just reviewed my logs to make sure I didn't hallucinate:

  **************** Jira starting... **************** 2025-03-07 13:29:00,098-0800 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] ___ Environment _____________________________ JIRA Build : 10.3.4#1010.3.4-sha1:d6812f2d35a143c1c5fc283d2f5a72582f40aaf1 Build Date : Wed Mar 05 00:00:00 PST 2025 JIRA Installation Type : Standalone 

...snipped...


{"userKey":"admin","date":1741373161608,"i18nKey":"upm.auditLog.install.plugin.success","entryType":"PLUGIN_INSTALL","params":["Jira Software Application","com.atlassian.jira.jira-software-application","10.4.1"]} 

[Trudy Claspill]

because the JSW upgrade button 

Is that a typo? Did you mean to say the JSM upgrade button?

Can you provide more information about the specific problems you have encountered?

Are you working on a JSM-only instance, or does it also include Jira?