A service desk admin/manager should be able to define rules for ticket resolution and closure based on their operational process of ticket handling lifecycle.
Setting up of business rules for ticket resolution/closure is important because -
The service desk solution should operationalize the business process followed in the organization
Remove any manual errors or miss outs during ticket resolution/closure
As a part of closure rules, a servicedesk agent should not be able to resolve or close a ticket
prior to adding a time entry.
without closing all the associated tasks.
prior to resolving/closing all the associated child tickets.
Quick snapshot below -
The closure rules will also work for the Android and iOS apps for Freshservice. Screenshots below-
Please add cannot close or resolve without a note being added?
This will be a great feature! Sometimes our agents are forgetful when it comes to adding time, myself included.
Will there also be the possibility to add these rules when the status is "Resolved" instead of closed? Many companies "finish" the interaction with the requester in the status "Resolved" and then anautomation closes the ticket.
Looking forward to this! Time tracking is integral for our operations.
It would also be useful to have closure rules that enable you to specify particular fields have to be filled in completed, before the ticket can be resolved/closed.
@Gonzalo, yes. We are building these rules for both "Resolved" and "Closed" status.
@James, today the asked feature exists. You need to head over to Admin -> Form Fields -> Click on a field -> Check the box that says "Required when closing the ticket"
Is there a timeframe on when this feature will be available?
Yes please provide a timeframe... This is necessary to ensure our technicians are properly tracking time spent on tickets