Which lifecycles create tickets
Mover 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.
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.What a ticket contains
Each ticket has a summary and a description. In ServiceNow, the summary is the incident’s short description. Dates use theYYYY-MM-DD format.
- Joiner
- Leaver
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
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.

