Parent and Child in service requests

Yes, come on guys. We really need this feature. Many of our users send us emails rather than go into the Service Catalog. Having our agents manually creating new SR's then having to Merge tickets takes too many unnecessary steps. 

Please give us a status on this? We could really used this workflow in our environment and it would save us a lot of time. 

I like that you have been able to add child tickets to SRs but, the problem with this is that the same information needs to be added for each child ticket.  That is a lot to ask our personnel to do with each New Hire.  We like that Tasks can be automatically assigned in the automator but, since we assign to a group...and not an individual, those tasks are difficult to find.  Since we cannot automatically spawn a child ticket in the automator(which would be nice), can we instead SEE the tasks in the ticket view filter?  Can that Type be added along with Incident and SRs?

I'd just like to bump this request/thread.

Our use case: We need an easy-to-use way for managers to request an off-board of an employee (via SR), but that manager will likely not know all the sub-systems the user needs to be removed from. When an Agent starts working the SR ticket, it would be helpful if they could add child tickets to dispatch to the admins of those subsystems.

With Freshservice as it works today, I can add additional "requested items" to the current SR, but because the SR is assigned to me, the admins of those other systems won't see it in their queue. I realize we could re-assign the ticket to them to complete their step, but that seems a bit awkward if we have several tasks that are better worked in parallel (than sequentially).

It seems like adding child tickets to existing SRs would not be a terribly difficult thing, since child-relationships exist, but obviously I don't know the constraints of the datamodel behind all this. Thanks for your great work! 

I have an additional use case for why this should be able to be added from the Service Request itself.

We have announcements that go out from various departments to various listservs, but they require approval and staging (because SharePoint) to make sure they push correctly. While we have multiple people that can handle the staging environment to ready these things for deployment, only select administrators can actually push them to the live server for a multitude of reasons.

Check boxes/Tasks do not properly track and create ownership for both of these steps, and reassigns for issues that the initial party has no access to breaks valid reporting metrics.

A simple button, which already exists on incidents, to "Add Child Ticket" (as it is dependent on the initial request anyway) would solve hours of hand-offs and headaches.

I'd like to add another scenario in which this is almost mandatory, and one that other users have brought up in the past: employee offboarding.

Because permissions are handled as far as access by multiple groups (which include some 3rd party vendors) each step off the offboarding removal process can end up behind handled by different administrators.

Adding checkboxes to the SR portal only works if the requesting supervisor is aware of and remembers everything the user had access to which is not always the case, setting these as child tickets that can then be resolved or assigned to the correct parties for resolution is mandatory for the process to be complete and smoothly handled.

Any updates on this from the FS team?

I'm with Rob... I need to be  able to add a  "Add Child Ticket" to an existing SR.  I would also like a way to automatically closing a parent ticket once all of the child tickets are resolved or closed.   I have several use cases including employee on boarding, off boarding and new customer set up that involve many teams.   Being able to create and link SRs (even ad-hoc SRs)  would improved my reporting, SLA management and development of our service catalog. 

Is there any update on this? Can you also confirm that child tickets DO work on a Service Request when they are specified as part of the Service Catalog Item design. However, child requests are not possible in Service Requests by viewing a ticket and creating a child ticket (like incidents are below):

Joe - as there been any update on this. We have recently adopted Freshservice, and are struggling to find a working model for handling Requests in a Parent-Child way

thanks

iain 

Wow,  I am saddened by the lack of concern that this request has gotten.  It appears that as product users/customers we have no real ability to get the requests that we need added to the product.  This particular request is just asking you to honor the parent/child ticketing process for service requests after the initial service request has been submitted.  

I feel like as a new user of the product and after looking at requests that literally go on for years that there is no recourse for betting requests handled.  

Sid - That's seems pretty harsh. As a user of Fresh Service I find the development team to be very good and focusing and prioritizing on what is needed most. 

Service Requests already do have the capability of adding child tickets but only at the time of logging. Since an SR is (or should be) a consistent and repeatable process, there should be no reason why new child tickets should need to be added once the SR is logged. I can understand the reasoning behind the first cut of the SR module in FS. Perhaps this is why they have delayed developing the feature of adding ad-hoc child tickets until now.

Incidents do have that ad-hoc capability and that is where we tend to use it most. Though we are trialing a new business process of just re-assigning tickets to the person working on it as it 1) gives the customer a better view of who is actually working on the ticket, 2) Does not create a bunch of tickets that the customer needs to keep up with, 3) provides all the activity tracking under a single ticket.

For us it comes down to looking at our processes and what provides the best customer experience at the portal.

Hi Patrick,

I understand your response.  I don't think I was trying to be harsh.  I really do question why this request did have some promises made then was dropped.  There are also other forum posts for the same question posted that have had responses for several years and then some very recently with no real response from the development team.

I have tried to look at the number of likes and questions with some of the other requests that are on the roadmap and am not sure how the requests are processed because they seem to have lower likes than some that have been out there for a while.  I realize I have a very incomplete picture of the number so I have no real opinion on that aspect.

I do feel that it is difficult to understand what is being worked on and why.  I feel that the process still needs a little work to feel confident in the feature request process.

As to the Service Request functionality, I feel that there obviously are customers that see the benefit of being able to add child requests to a master service request like can be done with incidents so I can say that it is a request that would others would be beneficial to the product.

I'll be honest I did speak out of a little frustration but I also get the feeling that others are frustrated with the request process as well, again I have no ability to really tell how many customers that would be,  but I am certainly not as frustrated as I was this morning once I cooled off.  I will try to give myself more time to process my frustrations next time before adding to the forums. :)

I have looked for opportunities to really help improve the FreshService product not just for my organization but based on what i've seen in other systems.  We choose FreshService over 6 other systems so we have a vested interest in asking for changes that will help make the product better.  My organizations also trying to encourage others to look at FreshService.  We are part of a Technical College network in our state and want to help other schools find the tools that will help them as well. 

Hello,

Our organization would also like to see the ability to create child tickets from the default service requests.

I understand that child tickets can be created in a service catalog, but the reality is that there will always be situations in our work where we receive new requests that do not perfectly fit our current service catalog offerings. This causes a lot of unnecessary manual work, where our agents must create a new SR ticket, copy the URL of the parent ticket into the child and vise versa. The child tickets get escalated to different teams or departments that must complete a different portion of the requests.

If this feature is enabled, we can also potentially pull reports on SR ticket with child tickets, which will help us to prioritize the generation of the next service catalog item as well. 

Thank you for reconsidering this feature.

Ats

Joe,

Thank you for the response on this.  Does it look like this is still going to be possible in October?  Looks like it is a feature that many would like to see.

Thank you for your work!

Thanks so much folks. I can see the link now when viewing child tickets to create a new child. I assume that the ability to create a child ticket is removed once a ticket has gone through an approval process. This is the way it is working right now. Which does make sense.

One of the parent - child functionalities that I ame looking for is linking the same child ticket to the parent request multiple times.

For example, we have a parent ticket for a Primary Location. That primary location may have 1-20 secondary locations. We have a child ticket for the secondary location. Unfortunately, it's a 1 to 1 connection so Once the requester fills out the primary section, if they have a secondary, they can fill that out the secondary request as part, however, if they have multiple secondary locations, they can't add in another secondary location child ticket unless submit a separate ticket.