Hey folks, running into a strange issue when trying to create a new Plan from an existing project. If you try to make one, a message just pops up in the corner saying that an error occurred with a link to Atlassian support. We checked the logs and it seems to be kicking back an 400 error bad request from the plan API. One of the errors mentioned that it couldn't find a valid sprint, so we made one just to test, gave it a valid start and end date, but that did not resolve the issue.
Here's one of the error lines:
2025-09-03 15:18:32,128 http-nio-8080-exec-110 url: /rest/greenhopper/1.0/sprint/2; user: userID INFO userID 918x29834x1 1uj018b IPs /rest/greenhopper/1.0/sprint/2 [web.rapid.sprint.SprintResource] GreenHopper REST method failed with SC = 400 - HTTP 400 Bad Request
Hello @Alex Trecartin
Welcome to the Atlassian community.
What version of Jira Data Center are you using?
Does this happen only when one particular project is specified as the source, or does it happen regardless of what project is specified as the source?
Can you create new Plans by specifying a filter or a board as the source?
Do all users get the same results?
Hey, thanks for the quick response. In order:
This is on version 10.7.3.
This happens regardless of which project is selected.
This happens regardless of which method you try to use to make the Plan.
So far myself on an admin account, myself on a user account, and the user who brought this to our attention (assigned as an admin on this particular project) are all running into the same behavior.
Let me know if there's any other information gathering I can do to troubleshoot this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you previously been able to successfully create a Plan? If so, what has changed in your environment since then?
Have you recently upgraded Jira?
Did you originally obtain Advanced Roadmaps my installing a plugin, or did you get it out of the box with your Jira Data Center installation?
Have there been changes in your network configuration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We've never previously tried to create a Plan. This is essentially a brand-new dev environment that we're using to test features and permission schemes before moving our projects to a production environment. One of the stakeholders who has used Jira in the past was asking about creating timelines/roadmaps/plans and that sort of lead us here.
No, we haven't updated recently, it's been on the same version since we spun it up.
To my knowledge, we haven't dabbled in any plugins aside from implementing SSO, this should just be the out of the box feature.
Re: the network configuration, it's possible. I just reached out to our security guys to see if they put in any restrictions after the test tenant was created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just a quick update, we're not getting that 400 status code anymore. Instead we're getting this really cool SQL error:
2025-09-09 15:42:57,977+0000 http-nio-8080-exec-42 url: /rest/jpo/1.0/plan/setup/projects; user: jiradev ERROR jiradev 942x2325x1 1ww74td IPs /rest/jpo/1.0/plan/setup/projects [c.a.r.c.r.provider.exception.DefaultExceptionMapper] Caught SQLServerException for select top 2 "configuration"."ISSUE_LIMIT", "configuration"."HIERARCHY_ISSUE_LIMIT", "configuration"."PROJECT_LIMIT" from ""."AO_D9132D_CONFIGURATION" "configuration"
com.querydsl.core.QueryException: Caught SQLServerException for select top 2 "configuration"."ISSUE_LIMIT", "configuration"."HIERARCHY_ISSUE_LIMIT", "configuration"."PROJECT_LIMIT" from ""."AO_D9132D_CONFIGURATION" "configuration"
We checked that table in the SQL server and it was definitely empty. After manually creating a valid entry, it's still throwing the same error when trying to pull records. Uncertain if this is helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is beyond my skill set to debug.
I recommend that you open a support case directly with Atlassian Support on this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, I think that's about where we're at. I appreciate you taking the time to try and assist with this issue.
Best,
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good luck!
It would be great if you report back here what you learn. Maybe somebody else will encounter the same issue and benefit from your experience.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.