- Title, device, reporter, description, high priority and the report and
close times are already stored in MANGEL columns and no longer repeated
- INFOTEXT keeps the report number, Verantwortlichkeit, Standort,
low/medium priority, dashboard source, resolver name and Maßnahme
- Reporter and description are appended when their column is missing or
too short (MANGEL_LANG holds 50, MANGEL_ERFASSER 30 characters)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Admins search MP-Feuer (vehicles, device assignments, location texts,
departments) and map entries to a Standort under Admin → Standorte;
each entity can only belong to one Standort
- The barcode lookup returns the mapped Standort (assignment before
location text before department), falling back to name matching that
also handles MP-Feuer's "name | call sign" assignment format
- Mappings are removed when a Standort is deleted
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Read-only device lookup endpoints for the app and public dashboards
- Device lookup reads all available STAMM fields (number, name, type,
manufacturer, call sign, inventory number, assignment, location)
- Entering or scanning a barcode looks it up after a short pause or on
Enter (without submitting the form) and fills empty fields: Gerät and
a Standort matching the MP-Feuer assignment or location by name
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Set MANGEL_OK, MANGEL_HDZ (Handzeichen of the closing user) and
MANGEL_TERMIN (close date) like MP-Feuer does when a defect is closed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Dedicated MP-Feuer SQL Server connection (MPFEUER_DB_* settings)
- Device lookup by barcode in BARCODE_NR/BARCODE_NR2 of the GEL, GFU,
GHR, GMP, GSL and GSO _STAMM tables; the close dialog shows the match
- New <PREFIX>_MANGEL row referencing the device via _INDEX, with the
fault's times, reporter, title, description and a full report;
global Handzeichen (MPFEUER_HANDZEICHEN, default SM) and the user's
MP-Feuer Handzeichen from the settings
- Inserts run in MP-Feuer transfer mode so its triggers keep these
values; texts are truncated to the column lengths
- The fault is only resolved after a successful hand-over and stores
the MP-Feuer reference
- Dry run test against a configured MP-Feuer database (rolled back)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Optional barcode text to identify the affected device, shown on the
fault cards, included in notification mails and matched by search
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- GET /api/v1/me/groups returns the user's groups that grant the admin
role, login access or a Verantwortlichkeit, with what each grants
- Settings list these instead of all groups from the identity provider
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- New per user setting under Einstellungen → Benachrichtigungen,
enabled by default for existing and new users
- PUT /api/v1/me/preferences only updates the fields that are sent
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- UI calls fault types Verantwortlichkeiten
- Admins maintain OIDC groups per Verantwortlichkeit
- Dashboard edit dialog selects which restricted history to show
- Settings show the user's OIDC groups
- Document SMTP and group behaviour, add SMTP settings to Helm chart
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Fault types (Verantwortlichkeiten) get OIDC groups; the history of a
restricted fault type is only visible to group members and admins
- Users' OIDC groups are stored on login
- Dashboards get an admin managed list of restricted fault types whose
history they may show
- New faults send a mail to all known group members except the
reporter; SMTP is configured via SMTP_* environment variables
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Users store a default filter (fault type, location, priority, status)
via PUT /api/v1/me/preferences, returned as defaultFilter on the user
- The overview opens with the default filter applied; buttons switch
between showing all faults and restoring the default filter
- Settings page gets a Standardfilter section
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Report form selects the location from the admin managed list,
free text location field removed
- Admin tab Standorte replaces Kategorien (without color picker)
- Filters, fault cards and kiosk show the selected location
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- New Location catalog (name, description, sort order, active) managed
under /api/v1/admin/locations; faults reference a location instead of
a category and a free text location
- Filter by locationId, search also matches the location name
- Legacy migration converts existing free text locations into Location
entries and drops the category column, constraint and table
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Providers like Authentik sign ID tokens with HS256 using the client
secret when no signing key is configured. Verify HMAC algorithms with
OIDC_CLIENT_SECRET and all asymmetric algorithms via the provider JWKS.
Also run OIDC discovery with a background context, since go-oidc keeps
it for later JWKS refreshes and a request context gets cancelled.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
go-oidc requires an exact issuer match. The configured issuer was
stripped of its trailing slash, which broke providers like Authentik.
Use the configured value as is and retry with the slash toggled.
Add an OIDC login flow test against a fake provider covering PKCE,
nonce, group based role mapping, single use state and logout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>