Task Tracking when integrating product for different customers

[Bára Hlynsdóttir]

Hi does it make sense to use task tracking when there are similar and/or same steps that need to be done when integrating a product for different customers. If so should each customer be defined as issue and then the tasks needed to be done be defined as sub-tasks? and can they then be re-used instead of always creating new tasks for each customer?

[Jack Brickey · Accepted solution]

If I understand your question clearly what I would recommend is that you would create a task for each customer and sub tasks under that for the various tasks that need to be done for that specific customer. Yes you would need to create new issues each time. You would not want to reuse issues as you would lose any history which would not be a good thing in my opinion.

[Bára Hlynsdóttir]

Yes you understood me correctly. 

So there is no way for me to create default task list to add to each issue (customer)? so I don´t have to be creating the same steps every time

[Jack Brickey]

You can absolutely do this by using Automation. I would likely create a Manually triggered automation rule that you could run as needed. It could create any number of tasks and subtasks as you need. Then after creating it you could edit to make it unique to the specific customer. I’m not exactly sure how that would be manifested but likely the Reporter would be the customers name.