Version History¶
This page consolidates all historical changelog entries for Arctyk ITSM. For the latest release notes, see the current changelog.
[0.6.0] – 2026-01-03¶
This release introduces a comprehensive comment system for ticket discussions, SLA (Service Level Agreement) fields for compliance tracking, and extensive developer documentation including component guides, testing best practices, and feature documentation.
Added¶
- Ticket Comments System: Public/internal comment threads with rich text editing and edit history
- SLA Tracking Fields: Response targets, resolution targets, and lifecycle timestamps for compliance metrics
- Lifecycle Timestamps: Automatic tracking of created, first_responded, resolved, and closed times
- Developer Documentation:
- 10 comprehensive component guides (3500+ lines)
- Complete testing guide with pytest patterns
- SLA management feature documentation
- Contributing guide with commitlint requirements
- Commit Message Validation: Enforced Conventional Commits via commitlint
Changed¶
- README features table updated with Comments and SLA Tracking
- All documentation updated to reflect v0.6.0 features
- Docker image versioning improved for release accuracy
Fixed¶
- Comment form AJAX submission
- Workflow audit trail integration
- Version extraction in CI/CD pipeline
Technical¶
- New Comment and CommentEditHistory models
- Comment API endpoints (GET, POST, PATCH, DELETE)
- SLA field additions to Ticket model
- Lifecycle timestamp automation via signals
- Comprehensive test coverage for comments and SLA
- Integration with existing changelog/audit system
Breaking Changes¶
None - fully compatible with v0.5.0
[0.5.0] – 2026-01-01¶
This release focuses on ticket workflow improvements, adding complete audit trails, inline field editing, and comprehensive workflow validation.
Added¶
- Workflow Audit Trail: Automatic changelog entries for all ticket status transitions
- Inline Field Editing: AJAX-powered editing for description, assignee, requester, category, project, and due date
- Inline Status Editing: Real-time status changes with workflow validation
- Rich Text Styles: Comprehensive CSS for TinyMCE content rendering
- TinyMCE Integration: Rich text editor for description inline editing
- Status History Timeline: Visual timeline of all ticket transitions with actor and timestamp info
Changed¶
- Ticket detail view redesigned with inline editing support
- Form validation enhanced for inline AJAX requests
apply_transition()function extended with request context and audit logging- Create/Edit ticket templates updated with consistent styling
Fixed¶
- PATCH request handling for inline updates
- Select field display (labels vs IDs)
- Date formatting in responses
- TinyMCE URL routing and initialization
- Asset admin crash fix
- Breadcrumb display in ticket forms
Technical¶
- PATCH endpoint at
/tickets/<pk>/inline/ - AJAX responses with validated, formatted values
- CSRF token handling via X-CSRFToken header
- Permission checks for edit access
- Full ChangeLog integration via Django signals
Breaking Changes¶
None - fully compatible with v0.4.x
0.4.4 – 2025-12-26¶
This release focuses on major infrastructure and workflow improvements, highlighted by the upgrade to Django 5.2.9 LTS and significant enhancements to CI/CD, deployment, and server management.
Added¶
- Django 5.2.9 LTS: Upgraded the core framework from 5.1.15 to 5.2.9, ensuring long-term support, improved security, and access to the latest features and bug fixes.
- Dedicated deploy user for Docs: Introduced a non-root user for Arctyk Docs deployment on the production server, improving security and separation of concerns.
Fixed¶
- CI/CD reliability: Refactored the GitHub Actions workflow (ci-cd.yml) to resolve SSH authentication issues, ensure correct branch tracking, and automate versioning with bumpver.
- Server-side git integration: Standardized git setup on the Droplet server, ensuring the deployment directory tracks the correct branch (main) and is always in sync with the remote repository.
- Dependency management: Recompiled and updated both dev-requirements and requirements to ensure compatibility with Django 5.2.9 and other dependencies.
Changed¶
- UI/UX improvements: Refactored ticket_details.html and updated TicketDetailsView for a more consistent and user-friendly experience, continuing the ongoing UI/UX modernization.
- Deployment separation: Improved the deployment process by clearly separating the Arctyk ITSM dev server and the Arctyk Docs server, reducing risk and simplifying maintenance.
Removed¶
No features or dependencies were removed in this release.
Technical¶
- Branch alignment: The production server now uses the main branch for deployments, eliminating issues caused by branch mismatches.
- Clean deploys: The deploy script now ensures a clean working directory before pulling updates, preventing local changes from blocking deployments.
- Security: SSH keys and user permissions were audited and updated to follow best practices for automated deployments.
- Documentation: Updated changelog and internal documentation to reflect new deployment and versioning workflows.
0.4.3 – 2025-12-26¶
This patch release introduces a polished, standalone login experience to Arctyk ITSM while preserving the existing functionality. The new login page replaces the default Django authentication form with a Jira/Zendesk–style card and brand header.
Added¶
- New login page with centered card design featuring Arctyk logo, branded heading, and full-width sign-in button
- Dedicated SCSS styling (
_login.scss) with flexbox centering and neutral background colors - Modular login layout (
auth_base.html) designed for future SSO/MFA extensions
Changed¶
- URL routing: Custom login view implemented in
config/urls.py - Authentication behavior: Dashboard now requires authentication; unauthenticated users redirected to login
- Login experience mirrors Jira/Zendesk patterns with gate behind login
Technical¶
- No model, migration, or business logic changes
- Upgrade from v0.4.2 involves only template and static asset updates
- SCSS rebuild required for styling updates
- New templates picked up automatically by Django loader
0.4.1 – 2025-12-24¶
Fixed¶
- Create Ticket (AJAX): Fixed HTML responses for AJAX submissions; now returns structured JSON (
success,errors,redirect_url) - Update Ticket (AJAX): Fixed flow to return JSON responses instead of HTTP redirects; validation errors returned as JSON with HTTP 400
- Resolved
Unexpected token '<'errors caused by Django rendering templates instead of JSON - Ensured required workflow fields (
issue_type,status) properly validated and surfaced to UI
Changed¶
- Refactored Create Ticket UI to Jira-style layout with clear separation of core and metadata fields
- Refactored Edit Ticket UI to be workflow-focused with prominent status handling
- Required fields visually emphasized in both forms
Technical¶
- Added explicit AJAX request detection (
X-Requested-With) - Standardized JSON response formats across endpoints
- Improved frontend error handling with defensive response guards
- Maintained Django CBV, CSRF, and TinyMCE compatibility
0.4.0 – 2025-12-24¶
This release marks a major UI/UX transformation with a Jira-inspired interface, modular SCSS architecture, and centralized version management.
Added¶
- Jira-Inspired UI Overhaul: New sidebar with density tuning, active indicators, and branding; new topbar with create action, search, notifications, and user menu
- Modular SCSS Architecture: Split into base/, layout/, components/, and views/ for improved maintainability
- Centralized Version Management: bumpver integration for automatic version propagation to
pyproject.toml,package.json, and runtime modules - Changelog Documentation: Version tracking and upgrade guides
Changed¶
- Ticket detail page redesigned with structured, issue-centric layout
- Navigation patterns aligned with Jira-style information density
- Base layout refactored for consistent sidebar + topbar composition
- Improved accessibility and spacing across core views
Removed¶
- Recurring Ticket System: Models, tasks, tests removed due to architectural refactor; feature will return in future
- Legacy bulk quick-edit UI
- Deprecated ticket workflow code paths
Fixed¶
- CI failures from orphaned recurring-ticket tests
- Sass build path resolution on Windows and CI runners
- Sidebar hover and active-state regressions
- Missing icons and alignment issues in topbar actions
Technical¶
- Django CBV patterns maintained throughout refactor
- Bootstrap 5 + SCSS foundation for responsive design
- Celery integration preserved for async tasks
- Full test suite compatibility
[0.3.0-dev.0] – Version Rebase from 0.7.0-alpha.0¶
Initial release after version rebasing, consolidating core features from early alpha versions into a stable development baseline.
Added¶
- Core ticketing system (create, edit, assign, comment)
- Initial workflow states and priorities
- Asset and project associations
- Django admin customizations
- Early UI foundation with Bootstrap
Changed¶
- Iterative improvements to ticket list filtering and sorting
Fixed¶
- Timezone handling inconsistencies
- Initial Celery task stability issues
[0.2.0-dev.0] – 2025-10-XX¶
Added¶
- Initial project scaffolding
- Authentication and user management
- Basic ticket models and views
[0.1.0-dev.0] – 2024-09-XX¶
Added¶
- Initial proof-of-concept
- Django project setup
- Development environment tooling
This release focuses on major infrastructure and workflow improvements, highlighted by the upgrade to Django 5.2.9 LTS and significant enhancements to CI/CD, deployment, and server management.
Added¶
- Django 5.2.9 LTS: Upgraded the core framework from 5.1.15 to 5.2.9, ensuring long-term support, improved security, and access to the latest features and bug fixes.
- Dedicated deploy user for Docs: Introduced a non-root user for Arctyk Docs deployment on the production server, improving security and separation of concerns.
Fixed¶
- CI/CD reliability: Refactored the GitHub Actions workflow (ci-cd.yml) to resolve SSH authentication issues, ensure correct branch tracking, and automate versioning with bumpver. Server-side git integration: Standardized git setup on the Droplet server, ensuring the deployment directory tracks the correct branch (main) and is always in sync with the remote repository.
- Dependency management: Recompiled and updated both dev-requirements and requirements to ensure compatibility with Django 5.2.9 and other dependencies.
Changed¶
- UI/UX improvements: Refactored ticket_details.html and updated TicketDetailsView for a more consistent and user-friendly experience, continuing the ongoing UI/UX modernization.
- Deployment separation: Improved the deployment process by clearly separating the Arctyk ITSM dev server and the Arctyk Docs server, reducing risk and simplifying maintenance.
Removed¶
No features or dependencies were removed in this release.
Technical¶
- Branch alignment: The production server now uses the main branch for deployments, eliminating issues caused by branch mismatches.
- Clean deploys: The deploy script now ensures a clean working directory before pulling updates, preventing local changes from blocking deployments.
- Security: SSH keys and user permissions were audited and updated to follow best practices for automated deployments.
- Documentation: Updated changelog and internal documentation to reflect new deployment and versioning workflows.
0.4.3 – 2025‑12‑26¶
This patch release introduces a polished, standalone login experience to Arctyk ITSM while preserving the existing functionality. The new login page replaces the default Django authentication form with a Jira/Zendesk‑style card and brand header. Aside from the new login, no other features or fixes are included in this version.
Added¶
New login page: Replaced the default authentication template with a dedicated auth/auth_base.html layout and auth/login.html template. The login screen now features a centered card containing the Arctyk logo, a "Sign in to Arctyk ITSM" heading, username and password fields, and a full‑width "Sign in" button. The layout is minimal and modular so it can be extended for SSO or MFA options in future releases.
Dedicated SCSS: Added STATIC_SRC/scss/auth/_login.scss to style the login screen. The stylesheet uses flexbox to center the card, applies neutral Jira‑like background colours, and gives the card padding, border radius, and a subtle shadow.
Changed¶
URL routing: Updated config/urls.py to register a custom login view that renders the new template. The route automatically redirects authenticated users away from the login screen.
Authentication behaviour: The dashboard (root URL) now requires authentication; unauthenticated users are redirected to the new login page. This mirrors behaviour in comparable ITSM platforms like Jira and Zendesk, where dashboards are gated behind login.
Removed¶
No features or dependencies were removed in this release.
Notes¶
This release does not modify any existing models, migrations, or business logic. Upgrading from version 0.4.2 to 0.4.3 should involve only updating templates, static assets and URL configuration files. If you encounter any issues, please verify that static assets are rebuilt (e.g., via your SCSS build pipeline) and that the new templates are picked up by Django's template loader.
0.4.1 – 2025-12-24¶
Fixed¶
-
Create Ticket (AJAX)
-
Fixed incorrect HTML responses being returned for AJAX form submissions.
- Create Ticket now returns structured JSON responses (
success,errors,redirect_url) when submitted via AJAX. - Resolved
Unexpected token '<'errors caused by Django rendering templates instead of JSON. -
Ensured required workflow fields (
issue_type,status) are properly validated and surfaced to the UI. -
Update Ticket (AJAX)
- Fixed Update Ticket flow to return JSON responses for AJAX requests instead of HTTP redirects.
- Validation errors are now consistently returned as JSON with HTTP 400 status.
- Preserved audit logging and changelog generation while supporting AJAX workflows.
- Resolved frontend parsing errors caused by non-JSON responses.
Changed¶
- Refactored Create Ticket UI to a Jira-style layout
- Clear separation between core issue fields and workflow/assignment metadata
- Required fields are visually emphasized
- Refactored Edit Ticket UI to be workflow-focused
- Prominent status handling
- Cleaner separation of issue details, workflow controls, and audit metadata
Technical¶
- Added explicit AJAX request detection (
X-Requested-With) to ticket create and update views. - Standardized JSON response formats across ticket create and update endpoints.
- Improved frontend error handling to defensively guard against non-JSON responses.
- Maintained full compatibility with Django CBVs, CSRF protection, and TinyMCE.
0.4.0 – 2025-12-24¶
Added¶
- Jira-inspired UI overhaul
- New sidebar with density tuning, active indicators, and branding
- New topbar with create action, search, notifications, and user menu
- Modular SCSS architecture
- Split into base/, layout/, components/, and views/
- Improved maintainability and isolation of styles
- Centralized version management using
bumpver - Automatic version propagation to
pyproject.toml,package.json, and runtime modules - Changelog documentation and versioning guide
Changed¶
- Ticket detail page redesigned with a structured, issue-centric layout
- Navigation patterns aligned with Jira-style information density
- Base layout refactored for consistent sidebar + topbar composition
- Improved accessibility and spacing across core views
Removed¶
- Recurring ticket system (models, tasks, tests)
- Removed due to architectural refactor
- Feature will be reintroduced in a future release
- Legacy bulk quick-edit UI
- Deprecated ticket workflow code paths
Fixed¶
- CI failures caused by orphaned recurring-ticket tests
- Sass build path resolution issues on Windows and CI runners
- Sidebar hover and active-state regressions
- Missing icons and alignment issues in topbar actions
[0.3.0-dev.0] – Version Rebase from 0.7.0-alpha.0¶
Added¶
- Core ticketing system (create, edit, assign, comment)
- Initial workflow states and priorities
- Asset and project associations
- Django admin customizations
- Early UI foundation with Bootstrap
Changed¶
- Iterative improvements to ticket list filtering and sorting
Fixed¶
- Timezone handling inconsistencies
- Initial Celery task stability issues
[0.2.0-dev.0] – 2025-10-XX¶
Added¶
- Initial project scaffolding
- Authentication and user management
- Basic ticket models and views
[0.1.0-dev.0] – 2024-09-XX¶
Added¶
- Initial proof-of-concept
- Django project setup
- Development environment tooling