jira ls - no issues => implement better error handling
See original GitHub issueJust installed jira cmd
and jira ls gives me no issues
.
I’m using jira cloud (not hosted jira).
I guess that something is happening under the hood but no error is thrown so I can tell what is the cause.
jira -V
v0.5.4
Issue Analytics
- State:
- Created 4 years ago
- Comments:24 (11 by maintainers)
Top Results From Across the Web
Implement better error handling · Issue #257 · atlassian-api ...
For some reason the JIRA server is randomly throwing authentication errors. I'll take this up with my IT group. however the python API...
Read more >Jira fails to start with UnsupportedClassVersionError in the logs
After upgrading an app (plugin), Jira may fail to start when it's next restarted and report an "UnsupportedClassVersionError" error in the logs.
Read more >Issues are not showing under child issues panel | Jira
Diagnosis. Verify if the issues link table and the link type are proper or not using the below queries. SELECT ls.id,ls."source",ls.
Read more >Jira Service Management Upgrade Failed With Error "Failed to ...
Problem. A pop up with the following error message appears during the Jira Service Management upgrade from the page ⚙ > Applications ...
Read more >Too many open files error in Jira server
To count the open files opened by the JAVA process, we can use the command below to get a count: ls -U /proc/\{JAVA-PID}/fd...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like some mixup on documenting the solution when using a token instead of a password. The issued referred to just above (#93) points to a commit that has nothing to do with documenting the solution here.
So to save some other folks time in figuring it out, here is what should be documented from my experiments ultimately leading to a successful connection for an OAuth-based login.
Navigate to your Atlassian token management page: https://id.atlassian.com/manage-profile/security/api-tokens
Create a token; call it whatever you want; but you should end up something like this:
Copy that token.
If you have already tried configuring
jira-cli
delete your~/.jira/config.json
file.Run
jira
to start the configuration again.Go through the dialog, but instead of entering a password, enter the token from line (3).
The output should be
No worries, thx for an effort. Documentation for it here: https://developer.atlassian.com/cloud/jira/platform/oauth-2-authorization-code-grants-3lo-for-apps/