Ticket Blueprint

Registered by Jacob Henner

Tickets will be the primary object created with AdmitOne. They will be accessible via mobile device (app w/API) or by standard e-mail printouts.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Jacob Henner
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Ticket Attributes:

Owner (Foreign Key)
Purchase Date (Date)
Event (Foreign Key)
Id (Autogenerated)
Validation Hash (Autogenerated Varchar)
Used [check in] boolean

Each ticket will have its ID and validation hash stored in a verifiable Datamatrix printed on the ticket. Event coordinators will be able to verify authenticity of the ticket using these, and will be able to see if the owner has already checked in. Event coordinators will be able to check for unauthorized duplication through this method, and devices will be able to retrieve purchaser info through API.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.