New to Atlassian tools what should I explore first?

[Anna Wilson]

Hi everyone,

I’m new to the Atlassian community and have been exploring the different tools and possibilities around Jira and Confluence.There are so many features and different ways teams use these platforms that it can feel a bit overwhelming at the beginning.For those who have been using Atlassian products for a while, what’s one thing you wish you knew when you first started?

Would love to hear any tips, habits, or lessons that helped you get more comfortable with the tools.

[VENKATESWARLU KURUVA]

HI @Anna Wilson,

welcome to the Atlassian community...
Great question — and yes, the ecosystem can feel overwhelming at first. Here's what I'd suggest to you on Day 1:

Start With the Core Two
Jira and Confluence are the foundation. 

Jira → Create a small project, build a board (Kanban is easier to start with than Scrum), and practice moving issues through statuses. Understand issues, epics, and filters. Once you're comfortable, explore JQL (Jira Query Language) — it's a game changer for finding exactly what you need.

Confluence → Create a personal space, write a few pages, and try templates (meeting notes, decision logs, retrospectives). Link your Confluence pages to Jira issues — that's where the real power begins.

Tips
Use Atlassian Community & University — Atlassian University has free certification courses. The Jira Fundamentals badge is a great starting point.

Explore Rovo (AI) — Atlassian's AI assistant can search across your tools, summarize pages, and help you find information faster.

[Martin Runge]

Hi @Anna Wilson,

Welcome to the Atlassian community!

If I could give you just one major tip that completely changed the game for me when I started, it’s this: Dive into the community Learning!

You can find it on this site by clicking the Learning tab in the top navigation bar. All free learning paths and courses showcase the platform's capabilities and how it integrates with all Atlassian apps and above.

[Joao Galego]

Hi @Anna Wilson ,

Welcome to the Atlassian Community.

One thing I wish I understood earlier is that Jira and Confluence work best when you start with the real team process, not with the features.

It is easy to get excited by boards, workflows, automations, dashboards, AI, and integrations, but the most important first step is to define what your team is trying to manage.

For example:

What type of work are we tracking?

Who owns each step?

What information must be captured?

What does “done” mean?

Where should decisions, procedures, and lessons learned be documented?

Once that is clear, Jira becomes much easier to configure, and Confluence becomes much more valuable as the knowledge base behind the work.

My advice would be: start small with one real use case, keep the workflow simple, document the process in Confluence, and only then add automation, dashboards, or AI features like Rovo.

The tools are powerful, but the real value comes when the process, ownership, and knowledge are clear.

[viet_trancong]

Hi @Anna Wilson ,

Great question.

If you familiar with Github, I can suggest you to use it to synchronize project documentation automatically using Github Actions, instead of copy-paste documents to Confluence every time you make changes to one project.

I am currently manage a lot of projects, all the documents are on Github, non-tech users are not very familiar with it. When I found the way to automatically synchronize it to Confluence. It's perfectly save time and effective.

I can easily share the document to stakeholders, update doc whenever changes are made, ask Github Copilot (AI) for reviewing the document before syncing is a plus.

Thanks,

[Jason Krewson]

Welcome Anna!

When I joined I explored the available groups and joined the ones that interested me most. I would recommend doing the same, Browse the community.