Status: Closed (View Workflow)
Affects Version/s: 7.4.1, 7.4.2, 7.4.3, 7.5.1, 7.5.0, 7.5.2, 7.6.0, 7.5.3, 7.5.4, 7.7.0, 7.6.4, 7.8.0, 7.9.0, 7.9.2, 7.10.2, 7.11.1, 8.1.0, 8.2.0, 7.13.6, 8.5.0
Fixed in Long Term Support Release/s:
Introduced in Version:7.04
Support reference count:43
Symptom Severity:Severity 3 - Minor
Bug Fix Policy:
Current Status:Atlassian Update – 11 Oct 2019 Hi everyone, We apologise for taking that long to revisit this issue. The estimate for resolution provided in the previous status update has been long exceeded. As Atlassian values openness, let us bring clarity to this case and explain how we currently deem the bug. The last time we investigated it, we have decided that neither its impact nor the interest it had gathered were sufficient for us to prioritise fixing it. We have now examined it once again and reached the same conclusion. The fact that the impact and interest growth trends have remained steady since the previous evaluation only confirms that we made the right call. This and our current product priorities are the reason why we are once again deciding not to include it in our bug fix plans for the foreseeable future. The bug will remain in the "Long term backlog" status. It denotes that while currently it is not as severe nor pervasive as other issues, it is within the cohort of bugs which are the strongest candidates for being included in the bug fix roadmap during future reevaluations of it. We understand how disappointing this decision may be, but we hope you will appreciate our transparent approach and communication. To understand how we organise and prioritise bug fix work I encourage you to read Atlassian Server Bug Fix Policy . More importantly, if you would like to find out what the Jira team is currently focused on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bug Fix Team
Exception: Uncaught TypeError: Cannot read property 'scrollTop' of undefined
Steps to reproduce
- Create a customfield with User Picker (multiple users) option.
- Associate the customfield to screen used by project.
- Edit Issue Detail View of a board where the issues from project above are shown to include the User Picker customfield. (Board -> Configure Board -> Issue Detail View)
- Click on the same issue from the backlog and from the issue detail view, try to edit the User Picker customfield.
- Add multiple users to the User Picker customfield from issue page (must add at least 2 users. If the field contains 0 or 1 user accounts, this error does not appear).
Issue can also be replicated by opening full edit screen.
JIRA 7.4.1 +
Either error will be thrown in the UI (that can be hidden by clicking on the X button):
- "Exception: Uncaught TypeError: Cannot read property 'scrollTop' of undefined"
- "DetailsException: TypeError: t.responseContainer is undefined"
In some cases, we see the stack trace as:
Another workaround consists in clicking on the user icon located on the right side of the "user picker" field, to open the "User picker" browser page, as shown in the screenshot below. By doing so, no error will be thrown the UI: