We're updating our terminology in Jira

'Issue' is changing to 'work item'. You might notice some inconsistencies while this big change takes place.

Create a journey type

Journeys give you the ability to build end-to-end processes that connect work items across multiple service and software projects. They provide you with a simple view of all the work that needs to happen to complete a process, and the relationships between all that work.

This helps you streamline all the various processes in your organization that may cross multiple departments, such as employee onboarding or offboarding that require action from different teams.

For example, as part of an onboarding process you may need multiple departments to complete various tasks. These could include work items such as managing personal details in H.R. projects, provisioning software in I.T. projects, down to booking orientation sessions in Facilities projects.

Every journey type created starts out as a Draft. This allows you to slowly build an end-to-end process and continue working with stakeholders while your progress is auto-saved. Once your ready for your journey type to start running, you can select Publish to activate it. Read more about publishing and journey states

Create a journey type

  1. From your service project, select Project settings, then Journeys.

  2. Select Create journey type.

  3. Give your journey type a unique name and select the request type you’d like to use as the journey parent; this will be the work item a journey will be built upon when it starts running.

    1. We recommend not using the same request type for multiple journey types as it may affect how you report on journeys in future.

  4. Select Create.

Once created, the trigger will be set for when your chosen journey parent is created, whether this happens manually or via Automation. Other triggers will available to use as the event that kicks your journey off in future.

 

Still need help?

The Atlassian Community is here for you.