Troubleshoot Ticket Creation, Missing Categories, or Missing Ticket Fields

This troubleshooting guide checks published Department/Category relationships, Ticket Field Department scope and plan access, required-field and attachment validation, plus customer or verified-guest authorization.

Where this fits in QC Support Ticket

New-ticket availability is assembled from Published Departments, Department-compatible Categories, plan/published Department-scoped Ticket Fields, attachment policy and the current customer/guest authorization path. A blank selector or failed submit should be traced through those inputs in order.

Primary location: QC Support Ticket frontend and administrator interfaces, depending on the permission or failure being tested.

Troubleshooting procedure

  1. Confirm the target Department is Published.
  2. Confirm the expected Category is Published and assigned to All Departments or specifically to the chosen Department.
  3. For a missing custom Ticket Field, confirm the effective plan supports custom fields, the field is Published, and its Department access includes the chosen Department.
  4. Check Required validation and attachment rules for a form that submits but returns an error.
  5. For registered customers, verify normal ownership/session permissions. For guests, verify guest submission is enabled and the verification workflow is being completed.

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.
  • Repeat the test with the least-privileged normal role affected by the feature; do not rely only on Super User behavior.

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.

Fast isolation test

  • Choose a known Published Department and verify at least one Published Category is assigned to it.
  • Temporarily test with a simple non-file Ticket Field in the same Department scope; this separates field-scope problems from attachment-policy problems.
  • Submit as a registered test customer first. If that works, test the verified-guest path separately.
  • If the form still fails, capture the exact validation message and the selected Department/Category/field values before changing configuration.

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.