-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
7.2.15, 8.0.0, 7.13.0, 7.12.3, 7.6.10
-
7.02
-
8
-
Severity 3 - Minor
-
11
-
Problem Experienced
Some of Jira Agile's gadget produce requests that result in "400 Bad Request" responses from the server.
Steps to reproduce
Create a board, and add any of the following gadgets to it:
- Agile Wallboard Gadget
- Sprint Burndown Gadget
- Version Report
In the developer tab, disable browser's cache and refresh the page.
Existing Behavior
Requests made by the gadgets to the URL http://localhost:2990/jira/plugins/servlet/gadgets/makeRequest fail with 400 error code.
Expected Behavior
The gadgets do not make requests resulting in such errors.
Notes
It does not look like the errors cause any harm, the gadgets work fine despite them.
The errors can cause unnecessary false positives in the monitoring tools though.
- mentioned in
-
Page Failed to load
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center