Convert Tickets into Plugins and Manager

Problem/Motivation

The CAS Tickets are currently handled with much duplicated code in every ticket type, and the ticket factory having a separate near identical method for creating and loading every ticket type.

Proposed resolution

Convert all of the ticket types to Plugins under a CasTicket(Plugin)Manager and Mapper.

Remaining tasks

• ✅ File an issue
• ➖ Addition/Change/Update/Fix
• ➖ Testing to ensure no regression
• ➖ Automated unit testing coverage
• ➖ Automated functional testing coverage
• ➖ UX/UI designer responsibilities
• ➖ Readability
• ➖ Accessibility
• ➖ Performance
• ➖ Security
• ➖ Documentation
• ➖ Code review by maintainers
• ➖ Full testing and approval
• ➖ Credit contributors
• ➖ Review with the product owner
• ➖ Release notes snippet
• ❌ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• Tickets to be converted from Ticket Class with custom handling, to a Plugin Manager and Mapper.

Release notes snippet

• @todo