Repository navigation
feat: add configurable ticket access, accounts and SLA targets - #92
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents can currently read and change tickets outside their departments through lists, reports, REST, widgets and direct child queries. Add opt-in department/account access across these paths, nullable ticket accounts resolved by the host, shared account/type routing conditions, and department/type SLA targets. All options default off; administrators retain access.
The shared WordPress query guard scopes reads and bulk mutations and validates child parents on writes. Validated tokens use their owner's access context, assignments and notification recipients are checked independently, and chat routing/acceptance reject ineligible agents before changing session state. Unsupported protected SQL fails closed; the documented trusted bypass restores nested contexts even on exceptions.
Account identities compare exactly, including case, leading zeroes and trailing spaces. Subject association fills only an empty account. Department changes preserve SLA clocks; deliberate policy reselection uses the original creation time. Settings and SLA forms expose the opt-in controls.
Schema upgrades preserve existing records, add nullable columns and an account index, install ticket links before API reads, and run on the configured package database. WordPress users remain on the host connection. The integration guide documents resolver hooks, SQL grammar, actorless jobs and rollout requirements.
Validation: