Implement the Ticket Order Model

[DioChuks]

In cases where the organizer or User wants to see their ticket orders & payments, this gives us transparency b/w both U & Os. It should have its necessary structure somewhat like this, feel free to suggest extra or update to it:

• id
• ticketType
• eventName
• status(boolean, 0 for pending, 1 for completed, 3 for failed)
• quantity(number)
• amount(decimal)
• zkIdMatch(boolean)
• privacyLevel(string)
• hasReceipt(boolean)
• datePurchased

you can drop a message in the community group if u need to contact me. Link in the README.md

[AliFikan94]

@AliFikan94 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'm pumped to contribute to BuidlZone-Labs/zicket-backend—a solid Express/TypeScript/Mongoose setup powering what looks like a ticketing/event management dApp or platform (likely integrated with payments, orders, and possibly blockchain/Stellar for secure transactions). Implementing the Ticket Order Model (e.g., Mongoose schema with fields like orderId, userId, eventId, tickets array [{ticketType, quantity, price}], totalAmount, status [pending/paid/confirmed/cancelled], paymentMethod, timestamps, etc.) is a core building block for order processing, inventory management, user history, and scalability—especially with relations to Ticket/Event/User models.Relevant experience:Designed and implemented Mongoose schemas/models for e-commerce/order systems in Node.js/Express backends, including nested arrays (e.g., order items/tickets), references (populate for events/users), virtuals/getters (e.g., computed total), enums for status, and indexes for fast queries (orderId, userId, status).
Handled full order lifecycles: schema validation (Joi/Zod), pre/post hooks (e.g., update ticket inventory on save, calculate totals), error handling for stock checks/duplicates, and integration with payment gateways (Stripe/mock or crypto).
Built related features in similar projects: CRUD for orders, pagination/filtering by status/user/event, atomic updates (e.g., decrement inventory), and tests (Jest + supertest/mongodb-memory-server) for schema integrity and edge cases (over-ordering, cancellations).
Familiar with TypeScript best practices: interfaces for models, discriminators if multi-type orders, and secure patterns (no sensitive data leakage).

I can deliver a complete PR with:New Mongoose schema/model for TicketOrder (with proper fields, validations, indexes, hooks).
Any necessary related updates (e.g., references to Ticket/Event models, inventory logic if tied).

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AliFikan94 to this issue.

[ReinaMaze]

Hi, I’d like to work on this issue.
I have experience contributing to open source issues.
I’ve reviewed the description and understand what needs to be done.
Kindly assign this issue to me
ETA: 2 days

[Jayrodri088]

I'll create a TicketOrder model and GET /api/ticket-orders endpoint exposing organizer/user ticket purchase history with the specified structure: id, ticketType, eventName, status (0=pending, 1=completed, 3=failed), quantity, amount (decimal), zkIdMatch (boolean), privacyLevel, hasReceipt (boolean), datePurchased. Supports filtering by userId/organizerId and pagination.

The endpoint provides transparency between users and organizers via role-based access (organizers see their events' orders, users see their purchases), with Prisma relations linking to Event, TicketType, and Payment tables. Returns { orders: TicketOrder[], total: number } with proper decimal precision and status enum mapping. ETA: 3 hours for complete ticket order transparency API.

[DioChuks]

@Jayrodri088 you will be unassigned if no draft PR has been opened from you, your ETA stated 3hrs.

[Jayrodri088]

@Jayrodri088 you will be unassigned if no draft PR has been opened from you, your ETA stated 3hrs.

Hey @DioChuks sorry it came late I had power issues hence I could not push