CLI - Could not retrieve issue list

getIssueList run with --verbose
+ java -Djavax.net.ssl.trustStore=./.keystore -jar ./lib/jira-cli-4.1.0.jar --server https://jiradev.XXXXXXX.com --user sys-jenkins_user --password '<password goes here>' --action getIssueList --filter 'Open needs notification' --verbose
Server address: https://jiradev.XXXXXXX.com/rpc/soap/jirasoapservice-v2
Successful login to: https://jiradev.XXXXXXX.com/rpc/soap/jirasoapservice-v2 by user: sys-jenkins_user.

Remote error: Could not retrieve issue list. Details: com.atlassian.jira.exception.DataAccessException: java.sql.SQLException: Fail to convert to internal representation
java.rmi.RemoteException: Could not retrieve issue list. Details: com.atlassian.jira.exception.DataAccessException: java.sql.SQLException: Fail to convert to internal representation
at org.swift.jira.cli.IssueHelper.getIssueList(IssueHelper.java:1196)
at org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:778)
at org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:122)
at org.swift.common.cli.CliClient.doWork(CliClient.java:392)
at org.swift.jira.cli.JiraClient.main(JiraClient.java:109)
f7d8e44a87fc7c2b240b957b9f128ff3c5e6984b logged out.

 

 

The user - sys-jenkins_user has permissions in the project to browse and edit issue. The filter 'Open needs notification' is owned by the user and shared with everyone. Here is the filter itself:

project = DOE AND issuetype = "Code Deployment Request" AND Environment != Production AND createdDate <= -30m AND status not in ("In Progress", Approved, "On Hold", Done)


When the filter is run in JIRA, it returns issues as expected. When run via the above CLI command, it fails with the remote error.

1 answer

1 accepted

JIRA is having a problem. What version of JIRA? There will probably be log entries in the JIRA log. You will probably need to report to Atlassian and include those logs. A JIRA restart may help.

As a workaround, try using the alternate jql parameter instead of filter. This may follow a different path in JIRA. Use direct jql or, if you still need to use the filter, the --jql "filter = 'Open needs notification'".

 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 14, 2019 in Jira

Updates to jira.atlassian.com give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

733 views 1 15
Read article

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