Can SMAX allow multiple task to be assigned to the ticket?

I believe this is being done on the task plan with SMAX - on what is the next step once assigning a ticket to a certain individual or group. Can we assign to different groups at the same time when a ticket is created? (And have task setup like e.g. Network Team : check on this ---- Server Team: check on this and so forth. (and are all the responses being tracked or are all the task being tracked?

Tags:

  • Verified Answer

    +1  

    Hi John,

    For this particular aspect what you are describing is indeed using the Task Plan. A good way of doing this is using say an Incident Model. That way you can define what the Task Plan should look like and what Teams should have Tasks assigned to them along with any other detailed information that would make creating the ticket and assigning it to the correct group.

    Here is an example of a basic Task Plan with 3 manual tasks:

    Here the 3 manual tasks that must be assigned as part of this incident. The Tasks can then have the relevant information added as to what they need to do and who owns that task. Whether the task is a showstopper etc.

    Then when an Incident uses the model:

    You can see if a Task has been completed and what tasks are still be completed. Along with the SLT status. Also by clicking on Edit Task you can access the details of the task and see the Task properties.

    click on Edit Task and then you can see the actual task record:

    Here you can see what work has been completed.

  • 0 in reply to   

     Is there a way to display running tasks? The customer prefers not to navigate to the Tasks tab to view them. Are there any built-in functions or links available to list associated tasks, which can be added to a new custom field displaying the active ones

  • 0   in reply to 

    Hi Mahes,

    There is the means of viewing Tasks from the MegaMenu. Then you can see what Tasks are for you, your Group, recently completed or All Tasks. From there you can see the Parent Entity that created the Task. You could them modify the view to only show running tasks.

    Here you can see a new view called Running Tasks. I've set the Phase ID to Implement/Running. You can see the two tasks highlighted are for the previous example I discussed with the Incident Model Task plan.

    This way the customer can view all running tasks and still see what the parent entity that created them.