Parent-Child (Sub-tickets) Use Survey

Our example use case involves an employee new hire, which requires multiple tasks to be
completed for the new employee.

Option 1

This option provides an area in the ticket settings to create a checklist of tasks associated with a new hire. When a New Hire ticket is created, this checklist will appear on the primary ticket. As tasks are completed, they can be checked off by the responsible individuals.

Pros:

  • Simple to set up and easy to use.
  • Provides a quick overview of completed tasks.
  • Single ticket associated with the new hire instead of multiple tickets.
  • Easily adaptable for use on project list, routine maintenance, and other use cases where a checklist is useful.

Cons:

  • No automated workflows are involved.
  • Multiple users need to be notified based on their responsibilities in the new hire process.

Option 2

This option leverages the current rules area of the software to create child or sub-tickets
associated with a new hire. When a New Hire ticket type is selected, the software generates the primary ticket for the new hire and creates sub-tickets for each related task.

Pros:

  • Automated workflows can be set up using the rules area to create and route sub-tickets.
  • Ticket routing is customizable, notifying each user of their specific role in completing the
    tasks.

Cons:

  • No central area to view the status of all tasks.
  • Multiple tickets are created for each new hire.
  • More complex and difficult to troubleshoot.

Option 3

This option also utilizes the current rules area of the software. Here, a primary ticket for the New Hire type is created along with the first sub-ticket. Once the initial sub-ticket is completed, the system generates the next sub-ticket, continuing this process until all tasks are finished.

Pros:

  • Automated workflows can be established using the rules area to create and route sub-tickets.
  • Ticket routing is customizable, ensuring each user is notified of their specific role.

Cons:

  • No central area to track the completion status of all tasks.
  • Sub-tickets are only created after the preceding task is completed, potentially delaying the overall new hire process. process.
  • Most complex and difficult to troubleshoot.