Cannot link issues after upgrade to Jira 7.5.0 Edited

After upgrading to 7.5.0, when we try to link an issue, we get a spinning wheel.

We have re-indexed the server and run the integrity checks which are all ok but linking issues is stilll broken.

All the other options in the More menu work.

3 answers

0 votes

Hi Michael,

Can you let me know what error is occurring in your Jira logs when you try to link an issue? 

You can open your logs in a terminal and tail them, and then try to link an issue again, and you should see more details on what is going wrong.

Kind Regards,

Thank you. I can't get an error to occur in the log when I try to link an issue.

I have seen another error that may, or may not be connected to this problem:

2017-09-28 11:34:53,028 hercules ERROR mdibble 693x38716x1 1h599bw /plugins/servlet/troubleshooting/view/hercules/execute [c.atlassian.sisyphus.DefaultSisyphusPatternMatcher] Truncated 9 lines to 5000. Max length: 6899

Thank you


Hi Michael,

That one isn't related; Hercules is our service that reads errors and compares them to known errors in our documentation and can help you try to determine the issue you've run into. 

Another thing you can try is opening the Developer Tools in your browser and go to the Network tab. Then you can try to see what is occurring in your browser when you link the issue.

You don't happen to be using IIS, do you? If so, you may want to have a look at this answer on Community regarding maximum URL segment length that might cause a similar issue.

One more thing - does this occur in all projects or only specific ones? 

Kind Regards,

Hi Shannon. Thank you. I have the following log which shows a script failed to load:

AJS's create element functionality has been deprecated since 5.9.0.
No alternative will be provided.
Use document.createElement() or jQuery.parseHTML(), or preferably use a templating library.  batch.js:235
Downloading resources:
js!/s/00871291df37b1a33bc9da66d0584cef-T/-hl9rji/75005/b6b48b2829824b869586ac216d119363/d737e9d3caf989a3698e9bfd51c741c3/_/download/contextbatch/js/jira.edit.issue,-_super,-jira.view.issue,-project.issue.navigator,-atl.general,-jira.general,,-jira.project.sidebar,-com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx/batch.js?agile_global_admin_condition=true&healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-GB&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&user-logged-in=true!order  batch.js:433
Downloading resources:
js!/s/a083d2da4d09908c930057d6444b44b9-CDN/-hl9rji/75005/b6b48b2829824b869586ac216d119363/91d71c290cf8d5fa3742ca060916cdd6/_/download/contextbatch/js/com.atlassian.jira.jira-issue-link-confluence-plugin:init-issuelink-confluence,com.atlassian.jira.jira-issue-link-remote-jira-plugin:init-issuelink-jira,-_super,-jira.view.issue,-com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx,-project.issue.navigator/batch.js?jira.create.linked.issue=true&locale=en-GB&richediton=true&user-logged-in=true!order  batch.js:433
GET,com.atlassian.jira.jira-issue-link-remote-jira-plugin:init-issuelink-jira,-_super,-jira.view.issue,-com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx,-project.issue.navigator/batch.css [HTTP/1.1 400 Bad Request 0ms]
GET,com.atlassian.jira.jira-issue-link-remote-jira-plugin:init-issuelink-jira,-_super,-jira.view.issue,-com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx,-project.issue.navigator/batch.js [HTTP/1.1 400 Bad Request 0ms]
TypeError: Argument 1 of Node.appendChild does not implement interface Node.  batch.js:173:292
Loading failed for the <script> with source “,com.atlassian.jira.jira-issue-link-remote-jira-plugin:init-issuelink-jira,-_super,-jira.view.issue,-com.atlassian.jira.plugins.jira-development-integration-plugin:devstatus-dialog-resources-ctx,-project.issue.navigator/batch.js?jira.create.linked.issue=... FRY-263:1

Thank you, Michael!

You didn't confirm if you were using IIS earlier. The post I linked was also showing 400 Bad Request errors and was due to the limit of the URL segment in IIS.

Can you confirm?

Kind Regards,

Hi Shannon

The link was very helpful. The problem was due to the UrlSegmentMaxLength on our server defaulting to its 260 character limit. I have now set this to 500 and issue links are now working and a lot of other problems with access have all disappeared now.

Thank you for your help to resolve this problem.


No worries, Glad I could help! :) 

Take care and Kind Regards,

Hello, improving "UrlSegmentMaxLength" from default (260) to 500 helped me too.

Thank you very much!



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

168 views 4 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you