MokoConsulting/MokoJoomCommunity
1
0
Fork 0
Code Issues 78 Pull Requests Packages Projects Releases 1 Wiki Activity

feat: Event ticket system with multiple tiers #3

New Issue
Open
opened 2026-06-02 19:15:26 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-02 19:15:26 +00:00
Owner
Copy Link
Copy Source

Summary

Ticketing system for paid events with multiple price tiers, capacity tracking, and QR check-in.

Schema

  • #__mokojoomcommunity_event_ticket_types (price tiers per event)
  • #__mokojoomcommunity_event_bookings (tickets purchased, QR tokens, check-in)

Requirements

  • Multiple ticket types per event (VIP, General, Early Bird, etc.)
  • Per-type pricing, capacity, and sold count
  • Booking with payment integration (Stripe/PayPal)
  • QR code generation for check-in
  • Check-in scanning
  • Refund workflow
  • Waitlist when sold out

Status: Schema created (01.08.00), helper needed

## Summary Ticketing system for paid events with multiple price tiers, capacity tracking, and QR check-in. ## Schema - `#__mokojoomcommunity_event_ticket_types` (price tiers per event) - `#__mokojoomcommunity_event_bookings` (tickets purchased, QR tokens, check-in) ## Requirements - Multiple ticket types per event (VIP, General, Early Bird, etc.) - Per-type pricing, capacity, and sold count - Booking with payment integration (Stripe/PayPal) - QR code generation for check-in - Check-in scanning - Refund workflow - Waitlist when sold out ## Status: Schema created (01.08.00), helper needed
jmiller added the pending: testing label 2026-06-02 19:52:02 +00:00
Sign in to join this conversation.
Labels
Clear labels
admin-ui
Admin interface work
 bug: critical
Critical bug blocking functionality
 enhancement
Feature enhancement or improvement
 membership
Membership/subscription related
 obsolete
No longer applicable after repo consolidation
 payments
Payment system related
 pending: testing
Feature built, needs testing before close
 regguard
Registration guard related
 social-login
Social login related
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels pending: testing
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomCommunity#3
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?