jira: 400 Bad Request
my company is using the cloud version of jira. our url is: https://my-company.atlassian.net so have a single line in config.yml:
endpoint: https://my-company.atlassian.net
jira ls -u=my-name -p=my-project
ERROR [cli.go:163] response status: 400 Bad Request
ERROR [util.go:196] Field 'resolution' does not exist or this field cannot be viewed by anonymous users.
ERROR [util.go:196] The value '=SANGRE' does not exist for the field 'project'.
ERROR [util.go:196] Not able to sort using field 'priority'.
any idea what could it be? Also, I couldn’t find a password arguments in the --help or the readme.
Thanks!
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 25 (24 by maintainers)
Commits related to this issue
- [#12] integrate with keyring for password storage and provide http basic auth credentials for every request since most jira services have websudo enabled with does not allow cookie based authenticatio... — committed to go-jira/jira by coryb 8 years ago
- [#12] integrate with keyring for password storage and provide http basic auth credentials for every request since most jira services have websudo enabled with does not allow cookie based authenticatio... — committed to pdericson/go-jira by coryb 8 years ago
Local-security-risk workaround tested by a coworker: store auth in the
endpoint:inconfig.yml. I had to urlencode the@symbol in my username (an email address) to%40.endpoint: https://EMAIL%40DOMAIN.COM:PASSWORD@ACCOUNT.atlassian.net/I have added some documentation for authentication strategies with
go-jira, so I think this issue is finally solved by one of the methods: https://github.com/Netflix-Skunkworks/go-jira/blob/master/README.md#authentication