Edit or Retire a Ticket Field Without Losing Historical Responses

This article explains safe editing/unpublishing/deletion considerations and why existing ticket field snapshots remain readable.

Where this fits in QC Support Ticket

The Support Portal is ownership-scoped. Registered users work their own tickets; verified guests use a signed, expiring verification/access path for the specific guest ticket. Department choice also controls which scoped Categories and Ticket Fields are offered during intake.

Ticket Fields are Pro/Max functionality in the current plan model. Field definitions can be global or Department-scoped, and file fields are additionally constrained by the site-wide protected attachment policy.

Primary location: Joomla Administrator → Components → QC Support Ticket → Settings → Ticket Fields / Portal and Ticket Settings.

Before you begin

  • Confirm the site currently has Pro / Max / All Access effective access before expecting the controls described here. A preserved configuration may still exist after downgrade even when the feature is locked.

How to do it

  1. Before changing a field, identify whether the change is cosmetic (title/help/order) or semantic (type/options/meaning). Avoid semantic reuse that makes old answers misleading.
  2. For a field no longer needed on new tickets, prefer Unpublish first.
  3. If deleting is appropriate, confirm historical ticket responses remain readable from the ticket snapshot/history before removing the definition.
  4. Test a historical ticket and a new ticket after the change.

Important behavior and limits

  • Prefer unpublishing/retiring configuration first when you need to stop future use but preserve historical context; deletion should be deliberate.

Verify the result

  • The field appears on the new-ticket form only for its configured Department scope and publication state.
  • Required/help/order behavior matches the saved field definition; existing historical responses remain readable after later field changes.

If it does not work as expected

  • If a field is missing, check Pro/Max effective tier, Published state, Department scope, and the selected form/Department before recreating it.

Community Discussion

For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.