how to build a new-hire ticket template in jira service management

TL;DR

Create one New hire onboarding request type with required fields for everything provisioning needs (start date, manager, department, title, location, device type), split the work into owned subtasks, and gate provisioning on manager approval. An automation rule closes the parent when the subtasks finish, so nobody babysits the ticket.

Steps

1. In the IT service project, create a request type called New hire onboarding with a plain portal name. Expected: it appears in the customer portal where managers can find it.
2. Add required fields: start date, hiring manager, department, job title, work location, device type. Expected: the form cannot be submitted without the fields provisioning actually needs.
3. Create the work breakdown as subtasks or linked issues: create accounts, order laptop, assign licenses, grant building access. Expected: each subtask has an owner queue, not just the parent assignee.
4. Wire manager approval before provisioning: the account and device subtasks stay locked until the manager approves. Expected: an approval step in the workflow that blocks the subtasks.
5. Add an automation rule: when all subtasks are Done, transition the parent to Done and notify the manager. Expected: no manual parent-ticket babysitting.
6. Test with a fake hire end to end. Expected: the ticket completes with every field filled and every subtask closed.

Use this when

• New hires arrive with half the info provisioning needs
• Onboarding steps live in someone's head
• Managers keep asking what the status is

Not for this skill when

• One-off access requests (use the access request form)
• Contractor onboarding with different steps (clone the template and adapt it)

Compatibility

• Jira Service Management Cloud: request types, workflows, automation rules
• The pattern works on Server or Data Center with the same building blocks

Variants

Different onboarding per department

Use one request type with conditional fields instead of ten near-identical templates. Fewer templates survive longer.

High-volume hiring waves

Add a bulk CSV intake option alongside the portal form so HR can submit twenty hires at once.

Why it happens

Onboarding touches four teams, and every missing field becomes a back-and-forth comment thread. The template forces the information up front, once.

Edge cases

• Start dates that move: reopen and edit the ticket rather than cloning a new one.
• International hires: add conditional fields for local device and legal steps.
• Re-hires: they need account reactivation, not fresh accounts; add a re-hire branch.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ius9j6NEgR-TsGtbJUdoTw