[Mohamed-Alkafory]

Closes #159

What this does

Adds admin-defined custom fields to tickets.

• Definitions (admin only, installation-wide): name, type (text, number, date, select), required, description, sort order, and active flag. Deactivating keeps existing ticket values; deleting permanently removes the field and its values. Select options that are in use can't be removed or renamed.
• Values: support, user/TAM and superuser can set them when creating a ticket; support can edit them on non-closed tickets. On existing tickets, user/TAM and superuser see them read-only, like Category, and all values become read-only once a ticket is closed.
• Default is none: with no fields defined, ticket pages are unchanged.
• Storage: new tables with typed, indexed value columns, so fields can be filtered later through Advanced Search (Advanced search #157).
• Definitions are cached, and every definition change invalidates the cache.

Screenshots

[Mohamed-Alkafory]

@jesperpedersen @sksingh2005 PTAL

[jesperpedersen]

@sksingh2005 Can you start on this ?

[sksingh2005]

Yes I would take a look

[sksingh2005]

Thanks for the thorough implementation @Mohamed-Alkafory! The core design, role permissions, caching/invalidation, and backend test coverage are
solid.
Before merging, there are two key items that need addressing:

1. Missing sortOrder input in admin UI (Blocker)

CustomFieldFormState and the form submission in src/frontend/src/pages/CustomFieldFormPage.tsx track sortOrder, and the backend supports it, but there is no input control rendered in the UI form. All custom fields created via the UI stay stuck at sortOrder = 0.

• Fix: Add a numeric input for sortOrder in CustomFieldFormPage.tsx.

2. Unbounded text_value on PostgreSQL B-tree index (Crash risk)

src/backend/main/java/ai/mnemosyne_systems/model/TicketCustomFieldValue.java defines a composite B-tree index idx_ticket_custom_field_text on (custom_field_id, text_value). In PostgreSQL, B-tree index entries cannot exceed ~2,704 bytes. Submitting text larger than that will cause PostgreSQL to throw a fatal index row size exceeds btree maximum error on insert/update.

• Fix: Add max-length validation in TicketCustomFieldService.java (e.g. max 1,000 or 2,000 chars) before persisting TYPE_TEXT values.

Minor Suggestion

• In CustomFieldResource.java, validate that SELECT custom fields have at least one option line defined upon creation.

[Mohamed-Alkafory]

@sksingh2005 Take a look

[sksingh2005]

The code changes look great now @Mohamed-Alkafory!
Could you please attach a couple of quick screenshots of the UI in pr description please or screen cast as it would be great for further contributors.

1. The Custom Fields admin management pages (/custom-fields list and create/edit form).
2. A ticket create and ticket detail page showing custom fields populated in the top section.

[Mohamed-Alkafory]

@sksingh2005 Does this look good, or would you like me to add any additional screenshots?

[sksingh2005]

LGTM .Thanks

[sksingh2005]

@jesperpedersen PTAL

[sksingh2005]

@jesperpedersen is little busy with pgmoneta and other work. He will review shortly.
Thanks for your contribution.