Hi, Developer Community! 
The first and second EAPs for Jira Software 9.15 and Jira Service Management 5.15 are ready for testing.
This is a Data Center-only release and it doesn’t support Server licenses. With Atlassian Server end of support, you’ll need to ensure you have a valid Data Center license before upgrading to Jira Software 9.15.0 and Jira Service Management 5.15.
You can download the EAP from this page. If you’re using maven.atlassian.com, here are the versions:
- EAP 01: 9.15.0-m0001 for Jira Software and 5.15.0-m0001 for Jira Service Management.
- EAP 02: 9.15.0-m0003 for Jira Software and 5.15.0-m0003 for Jira Service Management.
To find out more about breaking changes, new features, and introduced fixes in Jira Software 9.15 and Jira Service Management 5.15, check out the Jira Data Center changelog
If you have any comments, post them below.
Happy testing,
The Jira Data Center team
2 Likes
The link for the new attachment validator module is currently a 404
atlas-run and …
[ERROR] Failed to execute goal com.atlassian.maven.plugins:jira-maven-plugin:8.13.5:run (default-cli) on project test-new-version: Unable to find/resolve artifact.: The following artifacts could not be resolved: com.atlassian.jira.plugins:jira-plugin-test-resources:zip:9.15.0-m0003 (absent): com.atlassian.jira.plugins:jira-plugin-test-resources:zip:9.15.0-m0003 was not found in https://maven.atlassian.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of atlassian-public has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO] Running Shutdown Hook
1 Like
Hi,
What Platform level does Jira 9.15 have?
Is it Platform 6.5?
What is the state of REST V2? Does it fully support REST V2 already?
thanks,
Bernhard
1 Like
The link for the new attachment validator module is currently a 404
Sorry about that! The link should be working as expected now. However, the doc itself may contain links to resources that won’t become available until the public release of Jira 9.15.
atlas-run and …
We’ve published the missing artifact, so the issue should be resolved.
What Platform level does Jira 9.15 have?
Is it Platform 6.5?
What is the state of REST V2? Does it fully support REST V2 already?
@clouless: Jira 9.15 comes with Platform 6.5, which enables the migration of your plugin to RESTv2.
However, only Jira 10 EAP will deliver the Jira DC’s REST API endpoints and beans migrated to RESTv2, which we recommend to use as the the base of your App migration.
The core code changes for that EAP have been completed and we’re preparing to ship that EAP next week, or right after the Easter weekend.
What about grey api removal ?
@FabienPenchenat: The first EAP will expose RESTv2 and intended deprecations, and the actual change in the OSGi configuration is planned in subsequent EAPs.
3 Likes
Hi @JacekKrawczyk
thank you for the information but unfortunately I still have the same error, maybe it will take some time for these artifacts to be made available to the public?
[INFO] Finished at: 2024-03-22T12:09:49+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:jira-maven-plugin:8.14.2:run (default-cli) on project test-project: Unable to find/resolve artifact.: The following artifacts could not be resolved: com.atlassian.jira.plugins:jira-plugin-test-resources:zip:9.15.0-m0003 (absent): com.atlassian.jira.plugins:jira-plugin-test-resources:zip:9.15.0-m0003 was not found in https://maven.atlassian.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of atlassian-public has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO] Running Shutdown Hook
[INFO] jira: Shutting down
Exception in thread "AMPS product shutdown" java.lang.IllegalStateException: Unable to shut down products in shutdown hook
at com.atlassian.maven.plugins.amps.RunMojo.lambda$addStopProductsShutdownHook$0(RunMojo.java:244)
at java.lang.Thread.run(Thread.java:750)
Cheers
Adam
Hey @adam.labus,
the artifact is available in the public Atlassian repo, you should be able to see it yourself at https://packages.atlassian.com/repository/public/com/atlassian/jira/plugins/jira-plugin-test-resources/9.15.0-m0003/jira-plugin-test-resources-9.15.0-m0003.zip .
Maybe Maven did not attempt to check the remote repo on your second run and used the cached response. You can try to run it with “-U” flag to force check the remote repository and see if it helps.
Cheers,
Leo
1 Like
Hi @lvysochyn
thank you, now it works like a charm 
Cheers
Thanks for the info. Just to understand it right:
I can use REST V2 for my App in Jira 9.15 already and only the internal Jira REST endpoints of Jira itself will be V2 with Jira 10. correct?
Hi again @JacekKrawczyk
You talking about Jira 10 EAP 01 or Jira 9.15 EAP 01 because you said “The first EAP will expose RESTv2 and intended deprecations” ?
Thanks
By that, I meant the first Jira 10 EAP.
1 Like
Hello,
Recently when we were doing the compatibility checks for our plugins, we noticed that 2 of our plugins cannot be enabled on Jira 9.15. Such an error appears when running Jira 9.15:
___ FAILED PLUGIN REPORT _____________________
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 1 plugin failed to load during Jira startup.
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 'com.spartez.scrumprint.scrumplugin' - 'Agile Cards' failed to load.
[INFO] [talledLocalContainer] Error creating bean with name 'ofBizConnectionFactory' defined in URL [bundle://add1e44d-3a82-4ed4-9c6a-5417324be7fb_196.0:0/META-INF/spring/atlassian-plugins-components.xml]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.atlassian.jira.config.database.DatabaseConfigurationManager' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
[INFO] [talledLocalContainer] No qualifying bean of type 'com.atlassian.jira.config.database.DatabaseConfigurationManager' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
Was there anything that was changed related to Atlassian Plugin components in this Jira version? Seems like now DefaultOfBizConnectionFactory or DatabaseConfigurationManager requires some additional bean. I don’t see anything related to this in changelog, could you guys help me with this issue? Is there any information about this change somewhere?
Thank you!
I am getting strange errors with REST V2 when a non admin user requests an URL that is protected by @AdminOnly. Then I get HTTP 500 and in the logs it shows.:
13-Apr-2024 11:45:02.509 SEVERE [http-nio-8080-exec-3 url: /rest/foo/1/admin/customfields; user: bob] org.glassfish.jersey.server.ServerRuntime$Responder.process Error occurred when processing a response created from an already mapped exception.
13-Apr-2024 11:45:02.511 WARNING [http-nio-8080-exec-3 url: /rest/foo/1/admin/customfields; user: bob] org.glassfish.jersey.server.ServerRuntime$Responder.release Attempt to release request processing resources has failed for a request.
org.glassfish.jersey.server.ContainerException: java.util.concurrent.ExecutionException: org.glassfish.jersey.server.internal.process.MappableException: com.fasterxml.jackson.databind.exc.InvalidDefinitionException:
Multiple fields representing property "link": com.atlassian.plugins.rest.api.model.Status#resourcesCreated vs com.atlassian.plugins.rest.api.model.Status#resourcesUpdated
at org.glassfish.jersey.servlet.internal.ResponseWriter.getResponseContext(ResponseWriter.java:278)
at org.glassfish.jersey.servlet.internal.ResponseWriter.writeResponseStatusAndHeaders(ResponseWriter.java:128)
Reproduce
-
- Make an Endpoint
@AdminOnly
- 2: Make CURL request with
-H 'accept: application/json' and error appears
Works:
curl -u bob:5678 "http://192.168.178.73:8080/rest/myapp/1/admin/foo"
# response http 401
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>401</status-code><message>Client must be authenticated to access this resource.</message></status>
Does not work:
curl -u bob:5678 -H 'accept: application/json' "http://192.168.178.73:8080/rest/myapp/1/admin/foo"
# response http 500
<html>error foo ...</html>
ROOT CAUSE:
.m2/repository/com/atlassian/plugins/rest/atlassian-rest-v2-api/7.2.0/atlassian-rest-v2-api-7.2.0.jar!/com/atlassian/plugins/rest/api/model/Status.class
package com.atlassian.plugins.rest.api.model;
...
@XmlRootElement
public class Status {
@XmlElement
private final Plugin plugin;
@XmlElement(
name = "status-code"
)
...
@XmlElementWrapper(
name = "resources-created"
)
@XmlElement(
name = "link" // <================ DUPLICATE !!!!!
)
private final Collection<Link> resourcesCreated;
@XmlElementWrapper(
name = "resources-updated"
)
@XmlElement(
name = "link" // <================ DUPLICATE !!!!!
)
private final Collection<Link> resourcesUpdated;
...
Is this resolved in Jira 9.15 with REST V2? I am using platform version 6.5.9
@JacekKrawczyk Can you please check that, thanks. Pretty sure this is a bug in the library.
UPDATE:: I tested it on Jira 10, and there a correct error message in JSON format is returned:
{"message":"Client must be authenticated to access this resource.","status-code":401,"sub-code":-1}
UPDATE 2 I have raised ECOHELP-38931 since no one reacts to this and this blocks my app release for Jira 9.15
1 Like
Hi Team,
I’ve created
for the issue with the REST endpoints. I’ve set it as Critical for now as this is a blocker for customers to upgrade.
Regards,
James
1 Like