nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA 7.3.3 freeze when editing issue from issue filter

Tomáš Vlach_z6iizm

Hello,

we have JIRA Software 7.3.3 with JIRA Core 7.3.3 and whenever someone try to EDIT issue from issue filter (Issue search) its freeze, but whenever you open only the one issue you can edit it without problem. In Log Analyzer there are these errors.

NullPointerException when Authenticating from IE

Getting "Unknown error loading feed from" when subscribe Fisheye Gadget in JIRA

In the log there are lots of errors with illegal characters like this.

Caused by: java.net.URISyntaxException: Illegal character in path at index 34: /secure/attachment/95131/...

Do you think it could be something in common with the problem?

Accepted answers

AnnWorley

If you are getting an error in the browser during the freeze, it may be the issue described in this doc, which addresses one of the errors you mention: URISyntaxException with Illegal Character in Path when Accessing a JIRA Page

It doesn't seem like the FishEye gadget feed would cause the browser to freeze, and the error "NullPointerException when Authenticating from IE" would happen before the user had a chance to edit an issue.

Please let me know: What browser are you using, and can you edit issues from the filter in another browser?

All comments

AnnWorley

Please let me know: What browser are you using, and can you edit issues from the filter in another browser?

Tomáš Vlach_z6iizm

Hello Ann,

your fellow colleague from Atlassian Support already helped us.

It was problem about URL length which was set to 200 by default in IIS.

The resolution was modify the registry and increase the URL length.

Thanks for your answer

Tom

AnnWorley

Awesome - thanks for following up to let us know. It could help the next person who experiences this issue.

If anyone needs details, please see the Troubleshooting section on Integrating JIRA applications with IIS:

"Currently, the UrlSegmentMaxLength is set to 200 by default in IIS. To fix this, add a registry key to increase the max URL length and then reboot the server:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters] "UrlSegmentMaxLength"=dword:00000400

This will effectively set the maximum length to 1024."

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira