Onboarding to create TASK and not tickets

Hi @guidelagui have you taken a look at Sequential Ticketing for Employee Onboarding. Maybe this would help you while waiting for your suggestion.

Take care!

I have some complaints on this as well. We’ve always used Tasks in tandem with automators prior to trying out the Onboarding module. Tasks can live within a ticket without being a separate ticket (coupled with a ticket’s individual workflows), and do not flood a ticket board, nor the requester, with dozens of notifications.

Within the Onboarding module, child tickets’ creation does not currently permit any explanation/detail beyond a subject line with a character limit.

Additionally, our customized FreshService workflows used for new ticket creation and assignment apply to these child tickets - so it’s theoretically possible, if I have 20 child ticketed steps as part of the onboarding process, the Primary Manager may receive 20 ticket email alerts about setup tickets that bear no relevance to them. I’ll need to go back and edit each of those automators to account for this.

While normally I’d just make an automator that would assign these tasks automatically to Onboarding-generated tickets, I can’t seem to run automators to apply tasks to Onboarding tickets, unfortunately. These tickets appear to be excluded.

This is desperately needed! Onboarding and Offboarding tickets are both so noisy as they are now. 

Hi All,

We haven’t used the On/Off boarding requests that are built in due to our HR Team not taking up the chance to use the HR app.

Anyway we created our on New user & end user leaving request that go through the Workflow Automator. Once approved by Line Manager for the New User:

• Child tickets created for assets requested.
• Tasks created in the Parent ticket for Folder Access, Software etc

End User Leaving:

Once approved by the line manager this creates the child ticket if that user has assets to return and Tasks that are more like check list to follow through the correct process in removing the user.

All the Best,

Steve

Onboarding desperately needs a full rewrite. A typical onboarding process at our organisation includes about 50 tasks - these are now setup in difficult to maintain automation workflows.  Onboarding/offboarding needs the following improvements:

1. Build onboarding kits with groups of tasks as well as groups of tickets - we don't want 50 tickets per new joiner - tasks are the way to go.  
2. But, the automation workflow around tasks is very limited, you cannot even link task due dates to expressions in the workflow automator
3. Handle onboarding dates in a logical way - there's no built-in link between the onboarding date and the ticket/tasks due dates - this is crazy!  Onboarding processes are driven by the onboarding date, not the date the onboarding request was created.
4. There should be native functionality to have additional tickets/tasks trigger after the onboarding is over - there are dozens of followup tasks that occur after people join that need to be automatically tracked

I hope Freshservice is paying attention to this thread!

Agree - it needs work to me more functional and adaptive to companies needs - right now I am digging into how to automate the changing of the “requester” from HR to the reporting manager automatically on all the tickets - it’s a PITB!