🎉 Showcase Your Internal Atlassian Event

[#1]

G'Day Community Members,

Have you recently hosted an internal Atlassian-focused event—like a Jira best practices session, migration workshop, Confluence training, or an Atlassian roadshow at your company?

We’d love for you to showcase your event!

Sharing your story not only celebrates your hard work, but also:

• Inspires other community members with ideas they can borrow or adapt

• Highlights creative ways teams are driving Atlassian adoption

• Helps us understand what’s working inside organizations like yours

💡 What We’re Curious to Learn

When you share your recap, consider including insights like:

• Participation & Engagement
  How many people attended? How engaged were they—questions, chats, polls, hands-on activities?

• Content & Resources
  What topics did you cover? Did you use Atlassian resources (decks, guides, demos) or create your own?

• Impact & Adoption
  Are you seeing changes in how teams use Atlassian tools after the event (new projects, pages, workflows, requests)?

• Learnings for Next Time
  What worked particularly well? What would you change or improve?

These details help other leaders learn from your experience and run better events of their own.

📝 Event Showcase Template (Copy & Customize)

Use the template below for your Community post. Just copy, fill in the brackets, and adjust as needed.

---

Event Name:

[e.g., “Jira Best Practices for Project Leads”]

Atlassian Products Featured:

[e.g., Jira Software, Confluence, Jira Service Management, Atlas, Bitbucket, Trello]

🎯 Event Goal

[In 2–3 sentences, describe the purpose of the event.
e.g., “Help project leads standardize how they use Jira boards” or “Onboard new team members to Confluence for documentation.”]

📚 Agenda & Format

[Briefly outline the structure, e.g.:]

• 10 min – Intro & context

• 20 min – Live demo

• 20 min – Hands-on exercise or Q&A

• 10 min – Next steps & resources

🔑 Key Takeaways

• [Takeaway 1 – e.g., “Teams now understand how to use components and labels consistently.”]

• [Takeaway 2]

• [Takeaway 3]

🙌 Engagement Highlights

[Share a memorable question, a great discussion point, or an “aha” moment.
e.g., “Once we showed how to link Jira issues to Confluence pages, several teams asked to adopt that pattern immediately.”]

📎 Resources & Materials

[Link to anything you’re able to share publicly:]

• [Slide deck or recording (if available)]

• [Confluence templates or example pages]

• [Sample Jira projects/boards or workflows]

• [Any Atlassian resources you used or adapted]

📈 Early Signs of Impact

[Describe any changes you’re seeing or expecting, e.g.:]

• “More teams requested Jira projects after the session.”

• “We received follow-up questions about automations and reports.”

• “Confluence page creation increased in the week after the event.”

✅ What Went Well

[Call out what worked: format, timing, communication, activities, speakers, etc.]

🔄 What You’d Improve Next Time

[Be honest—this is what helps the community most. Timing? Level of depth? Tools? Promotion?]

📸 Photos & Screenshots (Optional but Encouraged!)

[Attach or link photos from in-person sessions, screenshots from virtual events, or snippets of boards/pages (with sensitive info removed).]

---

🚀 Ready to Share?

When you’re done filling this in, post it to this thread or create a new post by clicking on "Let's Discuss" at the top of the form so others can learn from your approach. Tag the Atlassian products you featured and any relevant groups so the right audience can discover your story.

Your experiences are shaping how teams everywhere adopt Atlassian tools—thanks for taking the time to share them!

[tradian]

Just submitted my first feedback after today's successful training session! 

[Chris Shernaman]

Thanks so much, @tradian! We'd love to hear the exciting highlights from your training session. Would you be able to share in this thread?

[tradian]

I work in the Technology group at an Insurance company. The session I hosted was the Jira Software Essentials Training, and there was a headcount of 30 participants, including myself. Our Instructor was Emma W. from Thinkado, she's great!

• Participation Levels: A very engaged group of 30 participants.
• Resource Usage: I did refer to the content library; however, since this was a training versus a CUG meeting, I leveraged my internal communications skills, tools, and references, a couple of Atlassian reference links such as "Getting started with Jira" on Atlassian Learning, and the "Jira Software Essentials" Exam page.
• Overall Experience: Overall, I had a positive experience. To be honest, I didn't expect the session to be very fundamental (easier than expected). We had various levels of experience with using Jira, so I hope to get critical feedback from participants.
• Product Adoption: Definitely, everyone in Tech is expected to be using Jira. We are also expanding to our business partners so increase in adoption is a yes.

I had two members who reached out with an interest in joining the Success Champions Program, @Chris Shernaman. Is the next step applying for the program?

I think it'll be great for me to have 1-2 other colleagues to support the quarterly CUGs at my company. 

[Prateek]

That’s a fantastic recap, @tradian! Hosting a Jira Software Essentials Training for 30 participants is no small feat — and it’s great to hear the group was so engaged. Your approach to blending Atlassian resources with internal communication tools shows a strong understanding of how to tailor content for diverse experience levels.

The fact that two members expressed interest in the Success Champions Program speaks volumes about the impact of your session. It’s exciting to see how training initiatives like this not only boost product adoption but also spark leadership and advocacy within the organization.

Looking forward to hearing how your team continues to scale these efforts and deepen Jira adoption across departments. Keep leading from the front! 💪 #CUGLeadership #JiraTraining #AtlassianChampions #CommunityImpact

[Eminium]

Born to be free

[Chris Shernaman]

@tradian , I previously emailed about the next steps, but we've received many questions from others interested in having multiple colleagues join as Success Champions to lead their internal communities. To clarify: Yes, your colleagues can apply to become Success Champions, provided they are actively helping to develop and grow your internal community through activities such as hosting best practice sessions, onboarding new users, and attending or leading their Center of Excellence (CoE) meetings to share Atlassian solutions, among other responsibilities.

Here are the criteria to become a Success Champion (all within a 90-day period):
• Host at least one training session
• Develop and conduct at least one onboarding session for new users
• Create a product knowledge Space to document governance for their users
• Promote Atlassian Learning to help users get certified
• Complete our Post-Meeting Survey after every event, whether small or large

Next steps:
1. Share the details of the Atlassian Champion program
2. Send them the application form - select Success Champion
3. Encourage them to join the Atlassian Community and this Company User Group discussion group

Please note, this program is still in Beta, and we have a waitlist. Meeting the criteria and staying active will help you progress on the track. If some customers fall below the activity threshold, we can move others from the waitlist into the Beta.

Please let us know if you have any questions. We're here to help!

[tradian]

Thanks, @Chris Shernaman

I've cascaded the message and am working with a peer to host our first internal workshop this year! I hope to share feedback with everyone. Initiation in progress!

[Chris Shernaman]

Keep us posted @tradian and please let us know if we can help. Looking forward to hearing all about your first workshop! 

[Lori Kaserman]

Event Name

Day in the Life of a Manager

Atlassian Products Featured

• Jira

Event Goal

For our managers to walk away with basic tools to help them understand project status using boards, filters, dashboards, and related Jira features.

Agenda & Format

• Board Overview – How to create boards and configure them
• Filters – Creating filters, using AI, JQL, etc.
• Dashboards – How to build more effective dashboards

Key Takeaways

Even though we have a lot of documentation and a “Jira Clippy” Rovo agent for questions and podcasts, many people still don’t understand the fundamentals of Jira.

Engagement Highlights

We demonstrated boards and how to filter them to easily see relevant work. One user reached out afterward and scheduled a 1:1 so I could help her set up her boards. She was very excited and was able to take the ideas we discussed, translate them into Plans, and create some plans for her team.

Early Signs of Impact

We’re having a follow-up meeting today, so I’m hoping they share some learnings and feedback.

What You’d Improve Next Time

Focus more on company-specific business scenarios. Potential areas to build additional documentation and guidance around include:

1. Senior Manager scenario
   You are a senior manager who wants to see how a project is progressing for an upcoming release and manage or plan future releases and work. Here are some tips and tricks.

2. Team Manager scenario
   You are a team manager who needs to:

   • Track release details
   • Manage day-to-day tasks for your team
   • Understand capacity
   • Reassign work quickly when someone is out
     Here are some tips.

3. Individual Contributor scenario
   You are a colleague focused on day-to-day tasks. Here are some tips.

[Ricardo Cardoso D_ Oliveira]

Event Name:
Atlassian Collections Day: Best Practices for Modern Teams

Atlassian Products Featured:

• Atlassian Teamwork Collection (Jira, Confluence, Loom and Rovo.)
• Atlassian Service Collection (Jira Service Management, Assets and Rovo)

Event Goal
The goal of this exclusive workshop was to deliver a comprehensive training on "Best Practices
for Modern Teams" to the VR team. The session focused on helping VR master Atlassian tools
to accelerate delivery, integrate workflows, and transform daily collaboration from strategic
planning to efficient operations.

Agenda & Format

• Intro & Context (15 min): Welcome coffee, alignment of expectations, and introduction to
  the Atlassian Collections philosophy.
• Deep Dive: Teamwork Collection (45 min): Live demonstration on how to connect
  strategic planning with operational execution and boost collaboration.
• Deep Dive: Service Collection (45 min): Practical insights into elevating Service
  Management and unifiying internal/external support.
• Q&A & Networking (30 min): Open discussion to address VR's specific challenges and
  brainstorm next steps.

Key Takeaways

• Integrated Workflows: The VR team gained a clear understanding of how to seamlessly
  connect high-level strategy with daily operations using Atlassian's ecosystem.
• Optimized Service Management: Attendees identified concrete opportunities to
  centralize and improve internal support and external customer experience.
• Enhanced Collaboration Culture: Discovery of new features designed to break silos
  and foster smarter, more agile teamwork.
• Engagement Highlights
  The energy and engagement from the VR team were outstanding. A major "aha" moment
  occurred during the Teamwork Collection presentation, where the team immediately visualized how integrating their strategic planning tools could eliminate manual reporting overhead in their current routines.

Resources & Materials

• Customized One Atlassian environment
• Atlassian Teamwork Collection Overview
• Atlassian Service Collection Overview 

Early Signs of Impact

• High enthusiasm and post-event follow-up questions regarding specific automation and
  migration possibilities for Jira Service Management.
• Immediate requests for specialized deep-dives into the newly presented collaboration
  features.

What Went Well

• In-Person Interaction: Hosting the VR team at our office fostered great energy, open
  communication, and high-quality networking.
• Content Alignment: The focus on practical "Modern Teams" frameworks resonated
  perfectly with VR's current organizational goals.

What You’d Improve Next Time

• Hands-On Lab: For future sessions, adding a 30-minute interactive sandbox exercise
  would allow the client to test the tools live during the event.
• Time Allocation: Both collections cover a vast amount of features; splitting this into two
  shorter, dedicated sessions could allow for deeper technical exploration.

Photos & Screenshots

LinkedIn post

[Tom Stafford]

Event Name: Rovo Studioで業務を効率化！ エージェント作成体験会

(Streamline your workflow with Rovo Studio! Agent creation experience session)

Atlassian Products Featured

Rovo Studio

Event Goal

The event was the first User Community session hosted in Japan for our organization and focused on hands-on learning with Rovo Studio. The purpose was to introduce participants to agents in Rovo Studio, specifically walking them through creating a "bug review agent" that can automatically assess Jira bug report quality and post improvement suggestions as comments. The session also aimed to set the stage for a community space where participants could share use cases, discuss challenges, and explore how AI agents can streamline everyday workflows across Atlassian tools.

Agenda & Format

Hybrid On-site / Remote

• 5 min - Intro & Objectives
• 5 min - Rovo Studio Overview
• 5 min - Sandbox access walkthrough
• 30 min - Guided Hands-on Exercises:
  1 - Create bug review agent
  2 - Refine instructions (formatting rules, removing text)
  3 - Adding skills
  4 - Testing and verifying agent
• 10 min - Q&A, Next Steps

Key Takeaways

• Hands-on format sparked immediate, real-world application even beyond the demo use case
• Protecting time for peer interaction is critical for our next event
• There is a genuine momentum for an ongoing Atlassian Community in our organization

Engagement Highlights

The ability to pre-set conversation starters left an impression on some participants that had not seen this feature in other AI agents. It is a small detail but showed that agents are not tools that just respond but that can guide users toward the right questions.

Resources & Materials

Currently all materials are in Japanese language only. Exercises were primarily adapted from resources shared by an Atlassian CSM.

Early Signs of Impact

• One participant created their own weekly report agent immediately following the session
• Another participant who had been building agents before the session admitted they realized they were doing some things incorrectly
• Many participants voiced that they love the idea of the User Community and look forward to the next event

What Went Well

• Atlassian's direct involvement for materials and coaching helped a lot. Our admin team member gained a great experience leading a hands-on training.
• Participants were engaged and proactively helped each other, truly embracing the concept of community.
• Participants left with actionable ideas and some acted immediately.

What To Improve Next Time

• Adjust duration or agenda to protect time for peer discussion
• Choose a use case that resonates more broadly, or let participants choose.
• Create stronger incentives for on-site attendance (90% attended remotely!)

[Mindaugas Dūda]

Event Name: Atlassian Community Event: Summer edition

Atlassian Products Featured: Rovo, Loom, Jira Software

🎯 Event Goal

Onboard users to Loom. Share Rovo and Jira use-cases from our internal teams.

📚 Agenda & Format

🔹 45 min - Shared how a multicultural team, working with 10+ stakeholders, organizes day-to-day work with Jira.

🔹 20 min - Talked about the experience of building a Rovo agent — was it a perfect match, or were there challenges along the way?

🔹 30 min - Alina Enache (our CSM) introduced Loom and showed how it supports daily communication and collaboration.

🔑 Key Takeaways

• Teams saw practical ways to structure day-to-day work in Jira when many stakeholders, teams, and priorities are involved.
• Participants learned what building a Rovo agent looks like in practice, including where it can bring value and where expectations need to be managed.
• Users were introduced to Loom as a simple way to reduce meeting overload, share context asynchronously, and improve collaboration across distributed teams.

🙌 Engagement Highlights

One of the strongest engagement moments came during the Rovo agent discussion. Participants were interested not only in what the agent could do, but also in the real challenges of building it, testing it, and making sure it provides useful answers.

The Loom demo sparked discussions about possible use cases, especially around replacing long written explanations or extra meetings with short video updates that provide better context.

📈 Early Signs of Impact

After the event we saw a spike in Loom video creation.

✅ What Went Well

The format was balanced between internal experience sharing and Atlassian-led product enablement. Having Alina Enache join as our CSM added extra value and helped connect the product demo with real use cases.

The event felt practical and relevant because it focused on real examples rather than only product features.

🔄 What You’d Improve Next Time

Next time, we could include short live exercises for Rovo. This would help participants try the tools immediately instead of only seeing a demo.

📸 Photos