Improve error handling and upgrade Jira Cloud to API v3#95
Improve error handling and upgrade Jira Cloud to API v3#95
Conversation
- Upgrade Jira Cloud client from API v2 to v3 - Add debug logging for deployment type, hosts, and API requests - Handle unknown deployment-type with error message - Add URL validation in RestClient to catch invalid URLs early - Add null client check before making API calls - Add support for GNOME Shell 48 and 49
Complete the API v3 migration for JiraServerClient (issue and filter methods) and update JiraCloudClient filter to use the new POST-based search/jql endpoint. Add spacing to popup menu for better readability.
Work tracking now continues indefinitely until the user stops it. The label shows elapsed time instead of remaining time.
|
Thanks for the PR. Would you mind splitting the API update and UX update into two separate PRs? Regarding the start-stop behavior, I'd like to keep auto-stop because it works best for me. I often tend to forget to stop time tracking, and this way I can be sure that my work has been tracked (especially when it's been auto-started by a branch checkout). |
The Tempo Server API v4 returns a single object instead of an array when creating worklogs. The old code only handled array responses, causing the callback to be called without the worklog result. This set _current_work to undefined, preventing subsequent updates.
|
I've tested the changes and indeed our server instance does not support API version 3. Please consider splitting this PR into one for the Jira + Tempo Cloud updates and another one to discuss the updated tracking behavior. |
- Add optional knock sound that plays with nag notifications (via paplay) - Add working hours and working days configuration for nag notifications - Add auto-stop timer as a toggleable setting - Propagate worklog API errors to user-facing notifications - Add AGENTS.md codebase architecture reference Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2 participants
No description provided.