[new Module] Ticketing system

[m3rashid]

A ticketing system can be used in a lot of ways. As a projects/tasks tracker, as a sales pipeline, as a customer support tickets etc.

A system where you have certain tasks and certain containers for those tasks, and you show it to the user segregated into those containers making it easier to manage. For example: In jira, it organizes and puts tasks into various containers depending on task status, story-points, projects etc.

Initial requirements

Users should be able to:

• Create a kanban board with a number of containers. Each board can have any number of containers from 1-10 (or any other hard upper limit). Each container can have multiple tasks/tickets
• Create task/ticket status (associated to the board)
• assign tasks to people in the workspace
• set deadlines for tickets
• set cycle time/duration (similar as scrum in Jira)
• analytics, grouped by cycles

Meanings

Task Status: Task statuses are used as grouping elements in the boards. They have a name and a an internal status, as to how this status should be treated as, which can be one of [todo, completed, pending etc.]

Cycle Duration: Users can define the cycle duration. Tasks are associated to cycle. The tasks/tickets shown in the current kanban board should be in the current cycle. After the current cycle duration is over, the whole board will be archived.

Archived boards: Once a board is archived due to end of cycle-duration, all the tasks marked as "not completed" will be transferred to the next cycle. There will be a screen interface where users can see their previous cycle boards.