📣 Sign up for Early Access Program (EAP) - Journeys for Jira Service Management

[#1]

Hi everyone! 👋

We’re excited to announce an Early Access Program (EAP) kicking off in April for a brand new feature in Jira Service Management - Journeys!

A way for you to automatically create work items (issues) across different service and software projects, allowing you to control when, where and how these work items get created.

This helps you increase efficiencies by streamlining all the various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding 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.

Sound interesting? Register your interest in the EAP!

How it works?

Add a trigger - Every journey starts with a trigger which listens out for a specific event to occur. Choose to either set your trigger for when a specific work item is created in Jira Service Management, or when a new worker is added to Workday if you have a connection setup.

Add a work item - Create work items automatically across different service and software projects so agents in your organization can action cross-department processes such as onboarding or recruitment.

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

Add dependencies - Pause the progress of a journey by stopping subsequent work items from being created. Coming during EAP*

Add actions - Create Automation rules for specific work items in your journey that may require additional functionality or flexibility. Coming during EAP*

Who we're looking for

If you're selected as a participant for this EAP, you’ll be among the first to get access to this brand new feature and receive improvements as we incrementally roll them out.

• You are on a Premium or Enterprise license

• You are an admin of a Jira Service Management project

• You are willing to engage with us and provide feedback on this feature

About the EAP

There will be some limitations during EAP which will be covered in support documentation. But don’t worry – improvements will be coming soon!

The main goal of this program is to make sure this feature meets your needs, which means your feedback is extremely valuable in helping to shape this feature. We’ll be reaching out to participants via a survey to know what worked well, what could be improved, and what else is needed to make this feature useful for you and your teams.

Register your interest in the EAP!

[YY Brother]

Wow! Awesome features. Thanks @Dushyant Sharma 

I have a client, who uses Jira Work Management to manage new hires onboarding/offbording. We also use JWM automations to setup a group of tasks to collaborate with all PICs related to this scenario. I'm wondering how and when I should persuade them to migrate to JSM HR solutions.

[Muhammad Fahad]

This is great @Dushyant Sharma . Looking forward to testing this.

[Yatish Madhav]

Thanks @Dushyant Sharma 

This looks relatively promising ... I say relatively because we do this currently in different ways already. One of them being Automation rules and another being some custom REST API methods.

My point - How is this different to Automation rules?

Not to shoot this idea/EAP down but shouldn't Automation rules rather be expanded or evolved more for this than adding it as a whole new section/feature (with the new term "Journeys")? Eg. publish/draft states, connection setup for additional third parties for use in the rules, etc.

I know there are a lot of Automation backlog and feature requests that I am personally watching that would be better suited and helpful for the Atlassian community - or am I wrong? :)

Thank you
Yatish

[Dushyant Sharma]

Hey @Yatish Madhav, first off it’s awesome that you’re using Automation for this. We’d love to hear more about this!

Journeys allow you to define and design employee lifecycle journeys like Onboarding or Offboarding, letting you stitch together multiple work items across multiple projects, all together in one place. It gives you a simple view of all the work that needs to happen to complete that process, and the relationships between all that work and the teams doing them when a journey runs.

As this is an EAP, we’ve only scratched the surface of what we plan to deliver, but in future, Journeys will also come with their own views of this work. Here you’ll be able to view all in-flight journeys to keep track of their progress, plus search and report on specific parts of a journey.

If you do want to bring more functionality to Journeys beyond connecting work items, that’s where Automation can come in where (very soon) you can choose to add specific Automation actions to these work items, such as send an email.

Let us know if you’d be keen to chat more on how your currently using Automation for this.

Thanks

[Martin Böhme]

Sounds very cool! Looking forward to trying it out!

[Yatish Madhav]

Thanks @Dushyant Sharma  that is interesting! 

From the explanation you have given, it still whispers "Jira Automation" in my head :) I might not fully understand the full difference yet. Also, when you say "define and design employee lifecycle journeys like Onboarding or Offboarding", i would almost bucket that as an automation template rather.

My point is only that it would make more sense (even if just to me :) ) to evolve/revamp Automation (eg to add more statusing, monitoring, advanced reportibility, etc) than to introduce a whole new feature/section. I think Jira already has many complexities in it for the standard user/admin. Am I missing the point of Journeys?

Would be happy to talk it through it and see a demo of it or see how it works to get a better/clearer understanding of Automation vs Journeys.

Thank you

[Dushyant Sharma]

Hey @Yatish Madhav, if you’re willing, we’d love to get you involved in our EAP so you can try Journeys out yourself so you can get more of an idea of the feature.

Is this something that you’d interested in? Once you’ve had a play around on the feature, we’d love to chat through your experience.

Please reach out to me on dsharma8@atlassian.com if you are interested.