Troubleshoot Assignment, Status, Priority, or Bulk Action Failures
This troubleshooting guide checks Department scope, active Agent/Status/Priority records, selected tickets, target Agent eligibility, session/CSRF state, and concurrent ticket changes before permissions are widened.
Where this fits in QC Support Ticket
Agent workflow failures usually come from a difference between the current ticket state and the requested action: Agent Department scope, target Agent eligibility, active Status/Priority records, mixed bulk selections, or a stale form/session after another change.
Primary location: QC Support Ticket frontend and administrator interfaces, depending on the permission or failure being tested.
Troubleshooting procedure
- Verify the acting Agent is active and scoped to the ticket's Department. QCST rechecks scope for assignment, Status, Priority and bulk operations.
- For assignment/reassignment, verify the target Agent is active and eligible for that Department.
- For Status/Priority, verify the target workflow item is active/published.
- For bulk actions, clear stale filters, select the intended current tickets and retry a small subset so one invalid/out-of-scope ticket does not confuse the diagnosis.
- Reload the ticket before retrying if another Agent may have changed it concurrently, and confirm the Joomla session/CSRF token is current.
Important behavior and limits
- Bulk actions do not bypass per-ticket Department authorization; QCST validates each affected record.
Separate authorization from workflow data
| Failure | First checks |
|---|---|
| Assignment failure | Check target Agent is active and scoped to the ticket Department. |
| Status failure | Check the Status is Published/selectable and mapped to a valid current behavior. |
| Priority failure | Check the Priority is Published/available; remember weight affects urgency ordering, not authorization. |
| Bulk action failure | Confirm every selected ticket is within the Agent’s allowed Department scope and that the requested action is valid for each current ticket state. |
Use one ticket before many
When a bulk operation fails, retry the intended change on one disposable/known ticket. If the single-ticket action fails too, fix that permission/workflow problem first. If single-ticket actions work but the bulk set fails, inspect which selected ticket differs in Department scope or current state instead of broadening the Agent’s permissions unnecessarily.
Verify the result
- Repeat the test with the least-privileged normal role affected by the feature; do not rely only on Super User behavior.
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.