Max length URL

[Rob Schalken]

I am building an url using groovy, but continue gets an error when building the url.

The url seems good. Is the length limited?

Here the log:

at com.atlassian.jira.issue.link.RemoteIssueLinkManager$createRemoteIssueLink$0.call(Unknown Source)
at com.atlassian.jira.issue.link.DefaultRemoteIssueLinkManager.createRemoteIssueLink(DefaultRemoteIssueLinkManager.java:78)
at com.atlassian.jira.issue.link.DefaultRemoteIssueLinkManager.validateUrlsForCreate(DefaultRemoteIssueLinkManager.java:335)
com.atlassian.jira.exception.CreateException: Invalid url, it must be a valid URI
2019-02-01 07:40:47,932 http-nio-8080-exec-5 ERROR ROBS 460x86816x1 1lswp51 84.105.226.128,127.0.0.1 /secure/CommentAssignIssue.jspa [c.o.s.jira.workflow.ScriptWorkflowFunction] Script function failed on issue: ITHO-137, actionId: 331, file: <inline script>
2019-02-01 07:40:47,932 http-nio-8080-exec-5 ERROR ROBS 460x86816x1 1lswp51 84.105.226.128,127.0.0.1 /secure/CommentAssignIssue.jspa [c.o.s.jira.workflow.ScriptWorkflowFunction] *************************************************************************************
2019-02-01 07:40:47,918 http-nio-8080-exec-5 ERROR ROBS 460x86816x1 1lswp51 84.105.226.128,127.0.0.1 /secure/CommentAssignIssue.jspa [c.o.s.jira.workflow.ScriptWorkflowFunction] url: https://jira.core-vision.nl/plugins/servlet/jiraxporter?template=Core%7CVision%20Release%20Note&jql=issueFunction%20IN%20linkedIssuesOf(%22(issueFunction%20in%20linkedIssuesOfRecursive(%27key%20%3D%20ITHO-137%27%2C%20%27Parent%20of%27)%20OR%20Key%3DITHO-137)%20AND%20issueFunction%20NOT%20IN%20linkedIssuesOf(%27cf%5B13200%5D%3DSW%20AND%20cf%5B13703%5D%3DMLG%20AND%20version_int%20<%202001000.0%27)%22%2C%22Fixed%2Fimplemented%22)%20AND%20type%20IN%20(%22Bug%2FDefect%22%2C%20%22New%20Feature%22%2C%2...

Any suggestions?

[Andy Heinzer]

I don't know of a max URL limit for Jira itself.  That said, it is very common for admins to use a reverse proxy with Jira and that proxy might have a limit to the size of a URL.  Check out the KB JIRA elements fail to render with HTTP 400 error

In that case, there is a known limit for Microsoft based proxies that you can overcome via a registry edit that is explained in that KB.  If you're not running your proxy on a Windows machine, then I would still be interested to see if you can look at a HAR file when a request like this is made to see what kind of error response you get in the browser.  This information should be helpful in understanding where the problem is occurring.