Idea: Additional public ticket alias and role-aware lookup

[PerchAnton]

I maintain RefMint, a TypeScript library for public references with type prefixes and a Bech32m checksum.

Use case

A customer calling a technical account manager could identify a support ticket with a checked reference.

Proposed change

Evaluate an additional public ticket alias and role-aware lookup; preserve existing ticket IDs and the five-role access model.

Alternatives

Keeping the current identifiers and lookup flow, or using a simple local alias, are valid alternatives. The extra field is worthwhile only if manual lookup is a real need.

Compatibility and validation

v0.1.0-alpha.1 is a GitHub package archive, not an npm release. It targets Node 22+ and Web Crypto browsers, with no runtime dependencies. The format may change; the checksum adds six characters and does not provide authorization.

I checked generation, formatting, parsing and typo rejection in the released package. I have not tested an integration here or measured benefits for your users. Would this optional workflow be useful?

[jesperpedersen]

@PerchAnton Sounds like a good idea. Try and create a pull request for it

[PerchAnton]

Thanks for the invitation, @jesperpedersen. I opened PR #207, with #206 tracking the scope.

It adds an opt-in copyable reference and lookup using the existing ticket ID, with no new database field or API. The UI is off by default. Lookup opens the existing support, superuser, TAM or user route; admin gets no control because that role has no ticket API permission. The code never grants access.

Locally, nine tests and the full frontend checks pass, and both enabled and disabled builds pass. A browser check with mocked API responses covered typing errors, navigation and clipboard failure. I have not run a real Keycloak/PostgreSQL permissions test locally.

The PR pins refmint@0.1.0-alpha.3, documents its limits, and uses Node 24 for frontend CI. RefMint is still alpha, and a practical benefit for Billetsys users is not yet proven. The dependency, format commitment and Node requirement remain review decisions for the project.

GitHub Frontend Checks and CI currently require approval before running (action_required); the passing results above are local.