Sub-statuses clearing after an incident is closed

[Will Meekings]

If a job is closed/resolved/cancelled then it clears all sub-statuses. Therefore when trying to run reports, we are unable to see whether a job has been on-hold and how long for if it is now closed/resolved/cancelled. In some instances, a job has clearly been on hold, e.g. the SLA for the job was 5 days and says met, however the job was resolved 3 months after being logged. The only way to delve deeper and find out how long the job was on hold for it to search for the job itself in the analyst portal, which is impractical when looking at reports for thousands of jobs.

I believe this was raised by another colleague on the Customer Support portal back in April/May, with the resolution stated as a product defect that will be rectified in a later update. Do you have any idea when this will be actioned as it is affecting our reporting?

[Gemma Morrison]

+1

[David Hall]

Hi @Will Meekings

Thanks for the post.  I can confirm that this has been addressed ready for the next update of Service Manager so that you will be able to control whether to continue to reset or maintain the sub-status when closing down the request.  

Kind Regards,

Dave.