Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,370,041
Community Members
 
Community Events
168
Community Groups

View in Issue Navigator link is not working (GH v 6.2)

When i click on "View issues in issue navigator" in Agile / GH board, it shows me following error

"Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized."

Also after wards if i click on , isues link available in JIRA it shows me a error message: "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down."

This time i also see following error in the logs catalina.out log file:

506x44265x1 mtwyf1 10.178.46.230,127.0.0.1 /rest/api/1.0/menus/find_link [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service

groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.

at groovy.json.JsonLexer.nextToken(JsonLexer.java:83)

at groovy.json.JsonSlurper.parse(JsonSlurper.java:73)

at groovy.json.JsonSlurper.parseText(JsonSlurper.java:59)

at groovy.json.JsonSlurper$parseText.call(Unknown Source)

at com.onresolve.jira.groovy.jql.IssuesInSprint.execMethod(script13729186275822048495194.groovy:117)

at com.onresolve.jira.groovy.jql.IssuesInSprint.this$3$execMethod(script13729186275822048495194.groovy)

at sun.reflect.GeneratedMethodAccessor1850.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

Has any one faced this issue...and know what is the resolution.. this is happening every time I follow these two steps, if i login and click on Issues link, it brings up all options properly..

4 answers

1 accepted

0 votes
Answer accepted

after upgrading to GRV to 2.1.8 this exception is not coming

The issue https://jamieechlin.atlassian.net/browse/GRV-256 seems to be different from above notified problem. we already have an issue created to track this at https://jira.atlassian.com/browse/GHS-9508 . We also ran script runner plugin and has same response 200 as shown here

JamieA Rising Star Jul 15, 2013

There's no point in creating a bug against GH because it's not their code. I agree it's probably a different issue, but can you create the bug in https://jamieechlin.atlassian.net/browse/GRV.

0 votes
JamieA Rising Star Jul 11, 2013

This link is added by script runner... can you check https://jamieechlin.atlassian.net/browse/GRV-256 and see if that's your issue (I don't think it is), if not create a new issue including the name of the board and screenshots and whatever.

Should you want to, https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-inSprint%28boardname%2Csprintname%29 has instructions on disabling that link without disabling the plugin entirely.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events