It is important for any scaled team to classify tickets (be it by collections of teams, backlog grooming status, org matrix, etc). The problem is that people wearing different hats will have their own focus. For instance, a delivery manager will really need budgeting or estimation fields to be populated, whereas an engineer will look for task-at-hand data. Team members tackling the delivery can be inconvenienced when forced to create a single ticket (say a bug), because classification field combinations are not easy to remember in the heat of the moment. Neelix task sets capability resolves this problem by allowing all necessary classification fields to be pre-configured for a single-ticket quick entry, structured ticket sets and subtask templates.