Skip to main content
Question

Show Kit Items on Multiple Tickets


ncorneau
Contributor
Forum|alt.badge.img+2

We’ve recently started using FreshService and I’m working on implementing the employee onboarding.  I’ve set up the stakeholders and they have the ability to select items from the service catalog with the kit that was built in the employee onboarding.

At this point, I’m working on setting up the ticket creation portion on the onboarding.  However, we have a couple people who are part of the initial user setup.  I’m wondering if there’s a way to have the items selected by the stakeholders show up on multiple tickets.  Right now, I have those kit items added to the parent tickets, but I am looking to have the items selected also show up on a couple child tickets.

Originally, I though these may be synced with the Parent-Child Synchronization app, but it doesn’t appear that this can be done that way.  Can this possible be accomplished in some other way such as an automated workflow?

I’ve included a screenshot as an example of what I’m looking at.  The image below shows a couple of the onboarding items that are currently showing up in the parent ticket.  Ultimately, I want to find a way to have these also show up on the child tickets.  If needed, this information can be added as note to the child ticket.  Any ideas?

 

Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+4
  • Skilled Expert
  • 12 replies
  • April 8, 2024

I’m in the exact same situation… I will be trying a couple things through workflow and let you know if I find out.


ncorneau
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • 5 replies
  • June 24, 2024
Patrick G wrote:

I’m in the exact same situation… I will be trying a couple things through workflow and let you know if I find out.

Hi Patrick!  I figured I’d check in just to see… Did you guys ever find a way to get the kits / service items requested to show up on the child tickets?


claytonsaid
Contributor
Forum|alt.badge.img+2
  • Contributor
  • 5 replies
  • March 11, 2025

Hi ​@ncorneau,

Not sure if you managed to find a better solution to this since the thread was started a year ago. 
My approach to overcome this hurdle was to either:
(i) Split the Service Item into parts (e.g. in your case Forticlient VPN - User Account, Forticlient VPN - Access) which can actually be hidden from the Service Catalog.  Then assign those to different agent group OnBoarding child tickets or

(ii) Assign Tasks to the Onboarding child tickets via workflow 


ncorneau
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • 5 replies
  • March 13, 2025

Hi ​@claytonsaid,

We just ended up having the agent navigate to the parent ticket for the time being.  However, I’m curious about what you mentioned.

I understand the portion about adding two service items in the catalog.  However, when you have the stakeholders or onboarding requester select the service items, do they need to select both?  Or you only include one of the selections for them to check of during the onboarding submission?

For example, if you have the requester selecting “FortiClient VPN - Access” during the initial onboarding request, how do you go about having the child ticket see up that information and add the “FortiClient VPN - User Account” to the child ticket?  I was under the impression there wasn’t a good option in workflow to have it read information from one ticket and have the information automated to a child ticket.

Let me know if my question doesn’t make sure, but I’m definitely interested in the solution you suggested.  Thanks!


Reply