Where do we go from here?

[Christianne Ribeiro]

Hello All,

Thanks for having me!

I've been in IT for a very long time and have used many tools throughout my career.

Atlassian tools, Jira and Confluence, came to me around 10 years ago.  This was when I've selected these tools for my team to use, as to align with the American colleagues where I was working then.

One of my team members and I even built a small manual, sort of instructions, on how to best use the tools, with pictures and lots of details.  It was a great effort.

Fast forward to now, after nearly four years in a DC, I've just started using Jira and Confluence in the Cloud, as we've just migrated.  Again, I had to investigate and prepare materials for my team to start using the tools in this new environment, UI and the new features. 

So, just wanted to check with the Community, where do we go from here?

Thanks

[Mia Tamm _Simpleasyty_]

Hi @Christianne Ribeiro, welcome to the Community!

It sounds like you and your team have already put a lot of effort into making Jira and Confluence work well in your environment, that kind of preparation is really valuable when moving to Cloud. The main difference you’ll notice is that Cloud evolves much faster than DC, with new features and UI changes rolling out regularly.

A good “next step” is to explore what’s new in Cloud compared to what you had in DC, and decide which features can bring the most value to your team (automation, integrations, analytics, etc.). The Community is a great place to ask specific questions as you encounter them, and you’ll find lots of people here who’ve gone through the same migration.

So in short: take some time to discover the new features, bring your team along with clear guidance (like the manuals you’ve already built), and don’t hesitate to share questions here – many of us have been in the same situation.

— Mia Tamm from Simpleasyty

[Vlad Zhigulin]

Hey @Christianne Ribeiro

Moving to Cloud can feel like starting over, but it also opens up some cool opportunities: automation, faster updates, and easier integrations. My advice would be to keep your team guides in Confluence as living docs, since things change often in Cloud, and use the Community whenever you run into something new — lots of folks here have been through the same journey.

Good luck!

[Marco Nowak]

We will stay at DC. If we will be forced to move to the cloud, we will choose a different tool than Jira/Confluence.

[Krista Williamson]

Hi @Christianne Ribeiro 

Welcome to the Atlassian (Cloud) Community! This post really resonated with me as I have also been working in Jira for a number of years and I am currently preparing for our migration over to cloud. 

I am living the "preparing materials for my team to transition" phase myself, so it is really nice to know I am not alone. Atlassian does a great job with training materials and helpful content, but nothing beats a guide that is tailored to how your organization uses the product. 

I am excited for this transition and all the new features available to us in cloud!

[Christianne Ribeiro]

Good luck!

From users' perspective, it's a bit of a shock with the Jira very different UI, so it's critical to prepare everyone as much as possible.

I've also formatted our Jira tickets to have our important fields where they can be better seen.

[Teodora V _Fun Inc_]

Hi @Christianne Ribeiro 

It depends on where you want to go, starting from here. Having an internal library with helpful materials is an essential step to successful migration to the new tooling (or the new old tooling). 

If your question relates to the development of these materials, I would say evaluate the team's needs. Is there a process that you can't replicate from DC to Cloud and needs documentation or a workaround? If you have additional marketplace apps, how do they complement your current Cloud state - that's another useful internal material.

And maybe it's nothing related to this :) A little more context may help.

[Christianne Ribeiro]

Thanks for the ideas Teodora.

It was an open question, on purpose, so I can could check the topics and journeys different people have/are having.

Definitely having a documentation page in Confluence for sharing the main links and onboarding points is very important.

Wouldn't go near reproducing Atlassian documents and training materials, but organising according to how we use it, seems the right way to go.

In terms of the actual migration, this has been managed (and ongoing) by a dedicated team outside my department.  I'm trying to facilitate the journey for my team.  If that helps, then, we could start sharing our findings.