Skip to main content
New Idea

Employee Onboarding - Share with department

Related products:Freshservice
  • October 11, 2024
  • 8 replies
  • 108 views

Peter Helto
Top Contributor ⭐
Forum|alt.badge.img+3

This is covered in two community posts but I did not see a formal idea request.

 

 

My HR dept. has more than 1 person putting in onboarding and offboarding requests.   They need the ability to see each others requests to prevent duplicate requests (which are occurring) and to follow up with status of a requests when the other person is out. 

I have suggested this to support via chat, email and zoom 3x.   

The easiest way to implement this would be to add the Admin view on the support portal to filter “Requests initiated by All”
 



 

8 replies

Forum|alt.badge.img+7

They’re gonna revamp the whole thing eventually, it’s a huge pain point, we’re all just kinda waiting for them to do it at this point. The way they implemented it is convoluted.


Peter Helto
Top Contributor ⭐
Forum|alt.badge.img+3
  • Author
  • Top Contributor ⭐
  • October 11, 2024

Totally agree.  It needs to be re-created as Form Fields which is my next idea request since that functionality is core to every other module.  It fixes a good chunk of the headaches.  If you wouldn’t mind helping upvote that too. 

 


Support told me they weren’t aware of users having issues and the only formal way to get them to consider is to open an idea request and get community votes.



Until they do, I’m hoping this is an easy thing to add since the view is already there for admins.


ITMike
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • December 6, 2024

@Peter Helto I’ve got an Automator that auto disables the requester as soon as the ticket goes in and that stops other team members form being able to create duplicate offboarding tickets on that person.


Peter Helto
Top Contributor ⭐
Forum|alt.badge.img+3
  • Author
  • Top Contributor ⭐
  • December 6, 2024

@Peter Helto I’ve got an Automator that auto disables the requester as soon as the ticket goes in and that stops other team members form being able to create duplicate offboarding tickets on that person.

@ITMike Yeah, I tried that.  The HR team then creates a ticket asking why they can’t select the user.  This is because they work different time shifts and can’t check with each other.  It’s faster for them to ask IT, unfortunately.  

The really just need transparency in what has been submitted by their team.


ITMike
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • December 6, 2024

@Peter Helto set the automator to also send the teams an email saying “X” was disabled.  It’s better than nothing, I would think with training they should just understand that if the name can’t be chosen it’s already been done, however, I understand the don’t want to take a chance thought process on their end.


Peter Helto
Top Contributor ⭐
Forum|alt.badge.img+3
  • Author
  • Top Contributor ⭐
  • March 20, 2025

@Kamakshi V   Hoping this one gets addressed along with form fields.  Maybe a rework of form fields tying into business rules will address this.


Kamakshi V
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • March 20, 2025

Ping ​@Jatin Rastogi ​@Tejas Chheda 


Kamakshi V
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • March 20, 2025

Hi Everyone,

I’m planning a Lunch & Learn thread based discussion with the ESM Product team in the community, where they’ll address key issues, gather feedback and answer all your questions. I’m hoping this will also be a great opportunity to discuss all-things ESM including the awaited features! Once I have more details, I’ll keep you all updated! 

If you think this would be helpful, feel free to give this comment a like!