kzbkowski/servicedesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
13a758779def5850b92e8ba550f968afb5f16215
servicedesk/CHANGELOG.md
Kacper 13a758779d
Some checks failed
Build and push image / build (push) Failing after 3m17s
Details
v1.0.1 
Documentation overhaul (TESTING/CONTRIBUTING/ARCHITECTURE/SECURITY/CLAUDE.md,
CHANGELOG.md, drop unmaintained src/README.md) plus CI-built Docker images:
Gitea Actions now builds and pushes the servicedesk image to the Gitea
container registry on Dockerfile changes, and compose.yaml pulls that image
instead of building locally. No application behavior changes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-22 01:29:43 +02:00

2.0 KiB
Raw Blame History

Changelog

All notable changes to this project are documented in this file. Format loosely follows Keep a Changelog.

[1.0.1] - 2026-07-22

Documentation and deployment/CI overhaul — no application behavior changes.

  • Added project docs: TESTING.md, CONTRIBUTING.md, ARCHITECTURE.md, SECURITY.md, CLAUDE.md; removed the unmaintained stock Laravel src/README.md.
  • Added .gitea/workflows/build.yml: Gitea Actions now builds and pushes the servicedesk image to the Gitea container registry whenever Dockerfile changes on main.
  • compose.yaml now pulls image: gitea.kzbikowski.pl/kzbkowski/servicedesk:${IMAGE_TAG:-latest} instead of building locally; mariadb pinned to mariadb:12.3; added a mariadb healthcheck and depends_on: condition: service_healthy for servicedesk.
  • Added tracked templates compose.yaml.example and .env.example (root) for the previously-untracked compose.yaml/.env.
  • Documented the new pull-based deploy flow and one-time registry login in install.md.

[1.0.0] - 2026-07-21

Initial release.

  • Ticketing core: categories/subcategories with per-subcategory custom fields, statuses, priorities, teams, attachments, message threads (public replies + internal notes), history log, merge/delete.
  • SLA rules per priority with a scheduled breach check (tickets:check-sla-breaches, every 15 minutes).
  • Response templates, quick actions, and per-event HTML email templates/ notification toggles.
  • Operator statistics dashboard (/operator/stats) with KPI tiles and breakdowns.
  • Branding/config panel: company identity, LDAP connection + user sync, SMTP, attachment limits, session lifetime, timezone.
  • LDAP authentication (LdapRecord) with local-account fallback.
  • REST API (/api/v1/...) via Sanctum, ability-scoped (tickets:read, tickets:write, dictionaries:read, users:read), with Swagger docs at /admin/api-docs.
  • Installable PWA manifest/icons for the client-facing area.
Reference in New Issue View Git Blame Copy Permalink