Implements API contract section 9: ticket resolution workflow with conditional status updates based on time entry existence. - Added query_time_entries_by_ticket_id() for POST /TimeEntries/query - update_ticket_resolution_safe() now checks time entries: * No time entries: sets status to 5 (Complete) * Has time entries: keeps current status (ticket remains open) This ensures tickets are only auto-closed when appropriate per the validated Autotask API workflow. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
3.7 KiB
3.7 KiB
Changelog - Claude Code
This file documents all changes made to this project via Claude Code.
[2026-02-05]
Added
- Autotask conditional ticket status update based on time entries (API contract section 9):
query_time_entries_by_ticket_id()- Query time entries for a ticket via POST /TimeEntries/queryupdate_ticket_resolution_safe()now checks for time entries and conditionally sets status:- If NO time entries exist: sets status to 5 (Complete) with completedDate and resolvedDateTime
- If time entries exist: keeps current status unchanged (ticket remains open)
Fixed
- Autotask ticket resolution update now correctly preserves exact field values from GET response in PUT payload.
The
issueType,subIssueType, andsourcefields are copied with their exact values (including null) from the GET response, as required by Autotask API. Previously these fields were being skipped or modified.
Added
- Restored Autotask PSA integration from branch
v20260203-13-autotask-resolution-item-wrapper:integrations/autotask/client.py- Autotask REST API client with full support for:- Zone information discovery
- Ticket CRUD operations (create, get, update)
- Ticket notes via
/Tickets/{id}/Notesendpoint - Safe resolution updates preserving stabilizing fields
- Query support for companies, tickets, time entries, deleted ticket logs
- Reference data retrieval (queues, ticket sources, priorities, statuses)
ticketing_utils.py- Utilities for internal ticket management and Autotask linkage- Database migrations for Autotask fields:
SystemSettings: Autotask connection settings, defaults, and cached reference dataCustomer: Autotask company mapping fieldsJobRun: Autotask ticket linkage and deletion tracking fieldsTicket: Resolution origin tracking
- Settings UI for Autotask configuration (connection test, reference data sync)
- Run Checks integration for Autotask ticket creation
- Customers page with Autotask company mapping
- Documentation files for Autotask integration design and implementation
- Added
docs/autotask_rest_api.md- Validated Autotask REST API contract based on Postman testing
[2026-02-04]
Added
docs/changelog-claude.md- Changelog file for tracking changes made via Claude Code- Setting to enable/disable daily dashboard redirect requirement (Settings > General > Navigation)
- New
require_daily_dashboard_visitcolumn inSystemSettingsmodel - Migration in
migrations.pyto add the column - Toggle in Settings General page under new "Navigation" card
- Default value is OFF (disabled) - users can navigate directly to any page
- New
Changed
- Converted changelog to English (all project documentation must be in English)
- Documented branch naming convention and build workflow in Claude memory
- Filled README.md with comprehensive project documentation based on source code analysis
Performance
- Added database indexes migration (
migrations.py) for frequently queried foreign key columns:JobRun: indexes onjob_id,job_id+run_at,job_id+reviewed_at,mail_message_idMailMessage: indexes onjob_id,location,job_id+locationMailObject: index onmail_message_idTicketScope: indexes onticket_id,job_idRemarkScope: indexes onremark_id,job_id
- Fixed N+1 query in
_recompute_override_flags_for_runs()- batch loads all jobs instead of per-run queries - Optimized Daily Jobs page with batch queries:
- Batch load all today's runs for all jobs in single query
- Batch infer weekly schedules for all jobs (was per-job query)
- Batch infer monthly schedules for jobs without weekly schedule
- Batch load ticket/remark indicators for all jobs