Issue with popup after JIRA upgrade to 5.2.1

Jay Sandals January 7, 2013

Recently we upgraded our JIRA instance to 5.2.1. Upgrade went fine but now we have an issue when trying to resolve/close issues. If we click Resolve/Close/Reopen/etc. we get the following error:

TypeError: document.getElementById("versions") is null

https://jira.<domain>.com/s/en_US-f9xs7t-418945332/813/6/1/_/download/superbatch/js/batch.js/eval/seq/1

Line 2

The popup never appears. However if we right click Resolve/Close/Reopen/etc and open in a new tab all functions work fine.

Another thing we noticed is if we removed the Fix Version/s from the screens the popup opens fine. However we need that field on all screens.

Any ideas how to fix this? Your help is appreciated.

Thanks.

2 answers

1 vote
Matheus Fernandes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 7, 2013

Check if this happens in different browsers as well. Also, try accessing JIRA through http://<ip-address>:<port> and see if the problem also happens. Other than that, try using Chrome's Developer Tools or Firebug in Firefox to troubleshoot why this error is occurring.

0 votes
Renjith Pillai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 8, 2013

Have you customized anything in announcment banner or custom field descriptions using javascript?

Enable safe mode and verify whether this appears.

Jay Sandals January 8, 2013

Same issue in safe mode. What is strange is if I remove Fix Version/s and change nothing else the popups work fine. However this is a field that we require and is not a custom field.

Renjith Pillai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 8, 2013

Is this happening only for one project for all projects? And what happens if you use the default workflow? Just checking these things to isolate that the error is not being caused by something special about the project configuration.

Suggest an answer

Log in or Sign up to answer