v1.0.18 issue listing assigned Jiras

[FilBot3]

Details

Version: v1.0.18
Reference: https://github.com/Netflix-Skunkworks/go-jira/releases/tag/v1.0.18
Operating System: MacOS Sierra

Issue Details

Using a previous version, I was able to list Jiras and work with them, but as of Version v1.0.18, I now get this error when trying to list Jiras assigned to me.

pd028300@M1711732 [09:43:49] ~/Downloads
$ jira ls --assignee=pd028300 -vv
DEBUG POST https://jira3.cerner.com/rest/api/2/search
DEBUG Setting DOMAIN to jira3.cerner.com for Cookie: atlassian.xsrf.token=BKYU-AELP-4429-2AWT|ec1505ce1f7a08e6426d1a60d5459f214f8dbe7b|lout; Path=/; Secure
DEBUG Setting DOMAIN to jira3.cerner.com for Cookie: BIGipServer~Prod~pool_jira3_prd_8080=723954442.36895.0000; Path=/; HttpOnly; Secure
DEBUG GET https://jira3.cerner.com/rest/auth/1/session
DEBUG POST https://jira3.cerner.com/rest/auth/1/session
DEBUG Setting DOMAIN to jira3.cerner.com for Cookie: JSESSIONID=3E155EEC3778DD61C8B53CF1CBD0439A; Path=/; HttpOnly; Secure
DEBUG POST https://jira3.cerner.com/rest/api/2/search
DEBUG Setting DOMAIN to jira3.cerner.com for Cookie: atlassian.xsrf.token=BKYU-AELP-4429-2AWT|73c1d915dd399d5f0f4f3159a5032fd6b37a0f7f|lin; Path=/; Secure
usage: jira list [<flags>]
alias: jira ls [<flags>]

Prints list of issues for given search criteria

Global flags:
      --help                   Show context-sensitive help (also try --help-long and --help-man).
  -v, --verbose ...            Increase verbosity for debugging
  -e, --endpoint=ENDPOINT      Base URI to use for Jira
  -k, --insecure               Disable TLS certificate verification
  -Q, --quiet                  Suppress output to console
      --unixproxy=UNIXPROXY    Path for a unix-socket proxy
      --socksproxy=SOCKSPROXY  Address for a socks proxy
  -u, --user=USER              user name used within the Jira service
      --login=LOGIN            login name that corresponds to the user used for authentication

Optional flags:
  -t, --template=TEMPLATE        Template to use for output
      --gjq=GJQ                  GJSON Query to filter output, see https://goo.gl/iaYwJ5
  -a, --assignee=ASSIGNEE        User assigned the issue
  -c, --component=COMPONENT      Component to search for
  -i, --issuetype=ISSUETYPE      Issue type to search for
  -l, --limit=LIMIT              Maximum number of results to return in search
  -p, --project=PROJECT          Project to search for
  -n, --named-query=NAMED-QUERY  The name of a query in the `queries` configuration
  -q, --query=QUERY              Jira Query Language (JQL) expression for the search
  -f, --queryfields=QUERYFIELDS  Fields that are used in "list" template
  -r, --reporter=REPORTER        Reporter to search for
  -S, --status=STATUS            Filter on issue status
  -s, --sort=SORT                Sort order to return
  -w, --watcher=WATCHER          Watcher to search for

ERROR Invalid Usage: No content to map to Object due to end of input

[FilBot3]

Downgrading to v1.0.17 works.

[coryb]

I am not sure how to reproduce this issue, is there any more details you can provide that would help me reproduce? perhaps you can share the output with -vv verbose options?

In general the code is working, we run regression tests against an atlassian.net service. Not sure what could have changed in the last release to cause problems.

[artem-nefedov]

Same is happening to me.
It seems that the issue is related to authentication, because after every attempt it asks for password again, even though the cookie file is created.

[FilBot3]

Updated description with full -vv output.

[FilBot3]

Using v1.0.17

pd028300@M1711732 [09:47:12] ~/Downloads
$ jira ls --assignee=pd028300 -vv
DEBUG POST https://jira3.cerner.com/rest/api/2/search
ETSTOOLS-9335: [Splunk][AWS] Which groups do I need to get access to Splunk?

[coryb]

I have been able to reproduce the No content to map to Object due to end of input error with a local instance of jira, trying to figure out why it is occuring now.

[coryb]

I have released a new version, which I think addresses this issue. It seems there was a subtle change in some of the dependencies that broke some logic replaying requests post-login. Please give it a try, hopefully it will fix your issues.