-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
7.2.0, 7.2.7, 7.4.1, 7.5.0, 8.15.0
-
7.02
-
35
-
Severity 3 - Minor
-
43
-
-
Summary
When opening issues in issue detail view on either Kanban or Scrum boards, request is sent to /rest/dev-status/1.0/issue/summary?issueId=undefined which receives a 400 Bad Request response because of the invalid issueId issueId=undefined.
Environment
JIRA Software 7.2 environment without any dev-tools integration*
Steps to Reproduce
- On a freshly installed JIRA Software 7.2 instance, create an Agile Board (Kanban or Scrum doesn't matter)
- Populate the Agile project with a few issues
- Enable the development tools network tab of your browser
- From the Agile board, select any issue so that it loads in the issue detail view panel to the right.
- Observe than when you select an issue there is a request to /rest/dev-status/1.0/issue/summary?issueId=
Expected Results
These rest calls actual have the correct issue ID appended and return a 200 response e.g. /rest/dev-status/1.0/issue/summary?issueId=10000
Actual Results
The rest calls are missing a valid issue id and appear like /rest/dev-status/1.0/issue/summary?issueId=undefined. Note issueId=undefined
Notes
Interestingly the problem corrects itself, if you have these instance integrated with Develpment tools (e.g. Bitbucket, Github etc.) to activate the dev panel. Once you delete the Development tools integration the problem re-surfaces.
- causes
-
-
- Closed
-
- is related to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
- relates to
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-14858] 400 Bad Request in response to /rest/dev-status/1.0/issue/summary?issueId=undefined when using issue detail view on Agile board
Dear Customers,
Thank you for taking the time to file and comment on this issue. We realise it still occurs and might be confusing when checking browser logs. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog.
Little explanation and severity of this bug:
We would like to explain that current log in console is not a symptom of wrong working instance. This is internal bug in development panel plugin which appears also in correct working instances.
Please continue watching this ticket for future updates and changes.
Best regards
Adrian Wojtasik
Jira Developer
We have the Development field restricted to one unused project because we don't want to have the performance impact that comes with it.
We still get this REST call made for every agile board in 8.20.10. These failures are noise in the Jira log files which distract from real error messages.
Please stop this papercut
This bug is present even if view development tools permission is not enabled for user.
Jira 8.7.1
/* module-key = 'com.atlassian.analytics.analytics-client:js-events', location = 'js/user-activity-xhr-header.js' */ define("atlassian/analytics/user-activity-xhr-header", ["atlassian/analytics/page-visibility"], function(c) { var e = "x-atlassian-mau-ignore"; var d = XMLHttpRequest.prototype.send; var a = window.fetch; var b = false; return { install: function() { if (!b && c.supported) { XMLHttpRequest.prototype.send = function() { if (c.isHidden()) { this.setRequestHeader(e, c.isHidden()) } d.apply(this, arguments) } ;
That i do not know. I have an open ticket with Atlassian. Just sharing our experience.
Hi Linda - thanks for the tip, it makes a world of difference to my Jira usage. Can I assume there will be a fix to support Chrome in the future though?
To Andrew - we have found the performance issue and drag and drop is browser related. Chrome 75 (74 slow but no drag and drop issues) and IE have major issues. We are now using FireFox and that browser works good. No performance issues or drag and drop.
also get this issue and am wondering if it is also the cause of very sluggish performance when I try to drag an issue around on the board.
To solve this, we used the rest api for the UPM to delete the Jira development tools integration system add on.
Hi!
We want the fix to be added Jira LTS version (8.4).
Regards,
Marek