> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lifecycle tickets

> Learn which ticket type Joiner and Leaver lifecycles create in ServiceNow or Jira, where each ticket goes, what it contains, and what you can't configure.

Track each new hire's onboarding and each leaver's offboarding in your ticketing system. When you turn on the ticket option in a Joiner or Leaver lifecycle, Oleria opens one ticket for each employee it processes and links it from the employee's event details page. Use this page to check that the tickets fit your service desk's process before you turn the option on.

## Which lifecycles create tickets

| Lifecycle | Option | When Oleria creates the ticket |
| :- | :- | :- |
| [Joiner](https://docs.oleria.com/governance/employee-lifecycle-joiner.md): HR-Triggered and Manual Entry | **Create a ticket to track joiner actions** | During the **Pre-Join** phase, before Oleria creates accounts |
| [Leaver](https://docs.oleria.com/governance/employee-lifecycle-leaver.md): HR-Triggered and Manual Entry | **Create a ticket to track leaver actions** | During the **Day of Departure** phase |

[Mover](https://docs.oleria.com/governance/employee-lifecycle-mover.md) lifecycles don't have a ticket option.

If no ticketing system is connected, the option is disabled. Connect one under **Settings** -> **Notifications** -> **Ticketing**. See [Ticketing](https://docs.oleria.com/workspace/ticketing-overview.md).

Oleria doesn't create tickets for employees processed while a lifecycle is in **Dry-run mode**.

## Where tickets go

Only one ticketing system can be connected to Oleria at a time, so you can't connect ServiceNow and Jira together. Lifecycle tickets and risk tickets go to the system you connected. A lifecycle has no settings for where its tickets go. Oleria uses the settings from your ticketing system connection, the same ones it uses for risk tickets.

| Ticketing system | Ticket type | Destination | Other values Oleria sets |
| :- | :- | :- | :- |
| [ServiceNow](https://docs.oleria.com/workspace/servicenow-ticketing.md) | Incident | The assignment group in the connection's **Assignment Group ID** | Caller: the Oleria service account. Category: `inquiry`. Impact: `2`. Urgency: `2`. |
| [Jira](https://docs.oleria.com/workspace/jira-ticketing.md) | Task | The project in the connection's **Project Key** | Priority: `Medium`. No assignee. |

## What a ticket contains

Each ticket has a summary and a description. In ServiceNow, the summary is the incident's short description. Dates use the `YYYY-MM-DD` format.

> [tab] Joiner
>
> **Summary:** `Employee Lifecycle - Joiners <lifecycle name> - <employee name> starting on <start date>`
>
> **Description:**
>
> * The employee's name, start date, department, job title, and manager
> * The employee's access bundles. When there are more than three, the ticket lists the first three followed by `...`.
> * A link to the employee's event details page in Oleria, where you can follow provisioning progress

> [tab] Leaver
>
> **Summary:** `Employee Lifecycle - Leavers <lifecycle name> - <employee name> terminated on <termination date>`
>
> **Description:**
>
> * The employee's name, termination date, department, and manager
> * A link to the employee's event details page in Oleria, where you can follow deprovisioning progress

## Known limitations

* A lifecycle can't send its tickets to a different ticketing system, ServiceNow assignment group, or Jira project than risk tickets use.
* In ServiceNow, Oleria creates incidents only. It can't submit a Service Catalog request, so you can't use an existing catalog item or its variables for lifecycle tickets.
* In Jira, Oleria creates Tasks only. You can't choose another issue type, and you can't set a Jira Service Management request type or queue.
* You can't change a lifecycle ticket's summary, description, or priority, or add your own fields.

## Contact us

For questions, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.