MokoConsulting/MokoSuite
0
0
Fork 0
Code Issues 73 Pull Requests 1 Releases 1 Wiki Activity

feat: expanded ticket automation with Joomla/CB event triggers and behavior options #151

New Issue
Open
opened 2026-06-04 12:06:19 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-04 12:06:19 +00:00
Owner
Copy Link
Copy Source

Summary

Expand the ticket automation engine beyond ticket lifecycle events to include Joomla system events and Community Builder events. Add behavior options for how events create or append to tickets.

New Trigger Events

Joomla Events

  • user_login - User logged in (admin or site)
  • user_register - New user registered
  • user_login_failed - Failed login attempt
  • content_save - Article/content saved
  • extension_install - Extension installed/updated

Community Builder Events

  • cb_user_register - CB user registered
  • cb_profile_update - Profile updated
  • cb_moderation - Content awaiting moderation
  • cb_user_banned - User banned

Scheduled

  • mokowaas.tickets.autoclose - Auto-close resolved tickets
  • mokowaas.tickets.sla_check - SLA breach detection
  • mokowaas.tickets.retention - Privacy retention enforcement

Behavior Options

When an automation rule fires and the action is to create a ticket:

  • append (default) - If an open ticket exists for the same user + category, add a reply instead of creating a new ticket
  • always_new - Always create a new ticket
  • skip_if_open - Do nothing if an open ticket exists for this user + category

Architecture

  • System plugin (plg_system_mokowaas) subscribes to Joomla events and delegates to automation engine
  • CB events via onAfterUserUpdate etc.
  • Scheduled task plugin registers 3 separate task types for independent cron schedules
  • Automation rules table gets a behavior column
## Summary Expand the ticket automation engine beyond ticket lifecycle events to include Joomla system events and Community Builder events. Add behavior options for how events create or append to tickets. ## New Trigger Events ### Joomla Events - [ ] user_login - User logged in (admin or site) - [ ] user_register - New user registered - [ ] user_login_failed - Failed login attempt - [ ] content_save - Article/content saved - [ ] extension_install - Extension installed/updated ### Community Builder Events - [ ] cb_user_register - CB user registered - [ ] cb_profile_update - Profile updated - [ ] cb_moderation - Content awaiting moderation - [ ] cb_user_banned - User banned ### Scheduled - [ ] mokowaas.tickets.autoclose - Auto-close resolved tickets - [ ] mokowaas.tickets.sla_check - SLA breach detection - [ ] mokowaas.tickets.retention - Privacy retention enforcement ## Behavior Options When an automation rule fires and the action is to create a ticket: - **append** (default) - If an open ticket exists for the same user + category, add a reply instead of creating a new ticket - **always_new** - Always create a new ticket - **skip_if_open** - Do nothing if an open ticket exists for this user + category ## Architecture - System plugin (plg_system_mokowaas) subscribes to Joomla events and delegates to automation engine - CB events via onAfterUserUpdate etc. - Scheduled task plugin registers 3 separate task types for independent cron schedules - Automation rules table gets a behavior column
jmiller added the joomlaphp labels 2026-06-04 12:06:19 +00:00
jmiller commented 2026-06-04 12:06:22 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/151-feat-expanded-ticket-automation-with-joo

git fetch origin
git checkout feature/151-feat-expanded-ticket-automation-with-joo
Branch created: [`feature/151-feat-expanded-ticket-automation-with-joo`](https://git.mokoconsulting.tech/MokoConsulting/MokoWaaS/src/branch/feature/151-feat-expanded-ticket-automation-with-joo) ```bash git fetch origin git checkout feature/151-feat-expanded-ticket-automation-with-joo ```
jmiller added this to the v02.35.00 milestone 2026-06-06 16:17:55 +00:00
Sign in to join this conversation.
Labels
Clear labels
architecture
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 bug
build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 duplicate
enhancement
generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 invalid
javascript
JavaScript code changes
 joomla
Joomla extension or component
 major-release
Major version release (breaking changes)
 minor-release
Minor version release (XX.YY.00)
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 needs-testing
Requires manual or automated testing
 patch-release
Patch version release (XX.YY.ZZ)
 php
PHP code changes
 priority: critical
priority: high
priority: low
priority: medium
push-failure
File push failure requiring attention
 python
Python code changes
 question
regression
Regression from a previous working state
 release-candidate
Release candidate build
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 standards-violation
Standards compliance failure
 status: blocked
status: in-progress
status: needs-review
status: on-hold
Temporarily on hold
 status: pending
Pending action or decision
 status: wontfix
This will not be worked on
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 test-failure
Automated test failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: release
Release preparation or tracking
 type: test
Test suite additions or changes
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-branch
Version branch related
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels joomla php
Priority Medium
Type Feature
Status —
Priority —
Type —
Milestone
No items
No Milestone v02.35.00
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuite#151
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?