Ticketing Solution

 A scalable ticketing solution for use within any company or organization. The application is password protected and developers are the only ones able to whitelist accounts that can gain access and sign up to use the system. Interactions with the application are different based on the type of user; developer, quality assurance, or general user.

 Users can submit tickets that have a title, description, and contain an associated file or image related to the project, as well as a priority level for the ticket. Once a ticket is submitted, a slack message is sent to notify the developers who can then claim those tickets to work on. All users can see who has claimed any individual ticket, but users who have created a ticket have the ability to edit the contents of only their ticket if they feel it is necessary. Tickets are organized according to priority level and Emergency Tickets have a red border so that they stand out from others that much more.

 Developers can see tickets that they have claimed on a separate page as well as set a complexity level that they feel is appropriate for the individual ticket. Once the ticket is ready developers can send the ticket over the the quality assurance team, who are also notified by a slack message, for review along with any associated URLs.

 Once the ticket has been reviewed by the quality assurance team they can send it back with any notes they might have regarding the ticket. Developers can see which member of the quality assurance team has reviewed their ticket in case they need to communicate directly. Once a ticket has been completed the developer can click the completed button, removing the ticket from the queue.

 If a ticket has a complexity level of 13 developers will be given the option to turn the ticket into a kanban project where they can create separate tasks amongst the developer team and and tackle the problem together.