Ticket Lifecycle Check

SkillDev tools

Lets your agent run end-to-end tests that verify the full ITSM ticket lifecycle from creation to closure.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Ticket Lifecycle Check skill

About this skill

Verify the real ITSM ticket lifecycle across creation, classification, assignment, comments, SLA, status transitions, resolution, closure, permissions, tenant isolation, audit, and persistence. Use for ticket workflow testing, CRUD/lifecycle regressions, or release acceptance.

What this skill tells your AI

The instructions your AI receives, as published by heidsoft/itsm in .trae/skills/ticket-lifecycle-check/SKILL.md and read by ahel’s review.

Use the repository Playwright flow

The canonical browser flow is:

cd itsm-frontend
PLAYWRIGHT_SKIP_CHANNELS=1 \
npx playwright test tests/e2e/business-flows/ticket-lifecycle.spec.ts \
  --project=chromium --workers=1

Backend must be available on 8090; frontend uses PLAYWRIGHT_BASE_URL or port 3000. Use existing auth fixtures and unique test data. Do not use mock backend data.

Validate the lifecycle

End user creates a ticket with required classification.
Ticket appears in requester and service-desk views as permitted.
Authorized agent assigns/updates it; unauthorized roles cannot.
Comments/attachments and workflow/SLA side effects are visible.
Status follows valid service-layer transitions.
Resolution and closure retain authoritative timestamps and audit history.
Refresh/revisit preserves the result.
A different tenant cannot access the record.

Do not assume delete is part of the business lifecycle; many enterprise records should be retained and audited.

Failure triage

Observe the expected API response for each mutation. If behavior fails, trace:

ticket page → ticket API client → router → controller → service → DTO/mapper → Ent.

Add or update a focused test for the broken visible outcome, then run:

cd itsm-backend && go test ./service ./tests/contract ./tests/rbac
cd ../itsm-frontend && npm run type-check && npm run lint:check

Signals

GitHub stars: 77
Forks: 18
Last commit: Oct 2026

Advanced

Item type: skill
Key: ticket-lifecycle-check
Source: github.com/heidsoft/itsm

github.com/heidsoft/itsm