Elena_Elevatic Atlassian Partner

Thanks @Viswanathan Ramachandran , that’s a sharp distinction and I agree with it. A page nobody opens is mostly clutter. A heavily used page nobody maintains is a real risk, especially once AI answers are built on it. This already works today. The Viewtracker Agent can list pages that were viewed but not edited in a given…

Hey @Carsten Severin _KUMAVISION AG_ Great breakdown of the governance angle especially — the "nothing lands unseen" request log is the part people underestimate until they've had a sync go sideways on someone else's instance.

hey @MeghnaP_LogicLemur Labs Good framing. The metric I'd add: how often does the agent's output get accepted without edits? An agent that "saves" 10 minutes but needs 8 minutes of review is a very different ROI story. Execution count hides that entirely.

Hey @Mary Van Roy Nice update. The search list covers Jira, Confluence, SharePoint, Google Drive — will Teams chat/channel history itself ever be a searchable source too, or does Rovo only use it contextually within the active thread?

hi @James Anderson thanks for this post, The mover case is the one that quietly does the most damage — joiner and leaver at least have a trigger event someone remembers to act on. A role change three teams later usually doesn't, so the old access just sits there next to the new access. If JSM is already the governance…

hey @Salome Ivaniadze Twinit This matches what we see with JSM Assets specifically — the schema gets treated like part of the migration deliverable, so once cutover is signed off it falls into a gap between "IT owns Jira" and "nobody owns this specific object schema." One thing that's helped: naming the Assets schema owner…

@Mia Tamm Simpleasyty @Maria Reisinger MetaFrazo — this is exactly the kind of thread I was hoping this post would start, thank you both :) Mia, "can it explain why this is the right information" is a better framing than anything I had in the post. It reframes the whole problem away from retrieval quality and toward…

hey @Karl from Ricksoft Thanks for the detailed comment. You're right that metadata and content are two different layers of a migration, and our feature focuses specifically on the metadata/classification side. For long-running migrations where DC and Cloud need to stay in sync throughout, having a dedicated solution for…

Hi @Mia Tamm _Simpleasyty_ Thank you, really well put. You're right that the hardest part is often preserving the structure and conventions around the content, not just the content itself. That's the gap we wanted to close with the automatic conversion into Content Categories, so teams don't have to rebuild that structure…

Thanks, @Zulfkar Ali! That's exactly the goal — cutting down the manual cleanup that usually comes with metadata during a migration. Glad the Forge-compatible path stood out too, that was an important design choice for us.

@Mary from Planyway Great overview! The "why can't I put a Task under a Story" one gets everyone. 😅 Worth adding: when people say "Jira won't let me customize the hierarchy," it's usually because they're in a team-managed project, where Epic → Story/Task → Subtask is locked. Knowing that vs company-managed solves half the…

Welcome to the ecosystem, @Evelin Bayer - codefortynine Great first post! Coming from copywriting before product marketing, your "how will people find this knowledge?" shift really resonated. Copywriters obsess over the reader's context—where they are, what they already know—so it's less about perfect structure and more…

Congratulations @Teodora V _Warsaw Dynamics_!! 

Thank you, @Rilwan Ahmed ! That's exactly it — the organizations that surface these early tend to have the smoothest migrations. In your experience, which of these tends to blindside teams the most?

@Daria Kulikova_GitProtect_io Love the "vault vs. liability" framing — protection and accessibility shouldn't be a trade-off. Real governance is enabling trusted, secure and usable access. Great read!

Hi @Evie Z_thanks for the heads up! I understand the rule and will keep it in mind for future posts.

Hello there! As usual, I’m sharing the latest poll results here: 13% of voters said that search limitations are the biggest problem 40% pointed to outdated content 33% felt there are too many pages to navigate through 13% mentioned poor page structure and organization The results suggest that content quality and…

Hey @Jack Dillon - Pallas Apps Nice overview of what’s involved in modernizing a Forge app beyond just adding features. The points about testing translations across languages and the practical benefits of design tokens for dark mode support were especially useful. thanks!

Hey @Dave Rosenlund _Trundl_ Interesting perspective on how the Atlassian admin role is evolving. The distinction between connecting systems and connecting operational context was especially relevant, and the point about AI amplifying existing process and governance issues feels very accurate. Thanks!

Hi @Benedetta De Martino , I totally agree with you. A well-structured Confluence documentation makes a huge difference. It not only speeds up research, but also reduces noise and helps teams find reliable information quickly. Thanks for your contribution!

Thank you @Carlos Garcia Navarro !

Hi, @Adil Alvi , I can suggest the app Metadata for Confluence. You can try it for free or book a no-obligation demo here.

Hi @Twinkle Dhawan_Sinergify Excellent breakdown! Especially the way you separate “vendor migration” from “customer responsibility.” That distinction gets missed a lot, and it’s where many teams underestimate the real effort. Also appreciate you calling out the practical Forge constraints (runtime, module parity, auth, and…

Hello everyone! As usual, I'm posting the results of our poll: * Attending in person: 57% * Joining online: 33% * Following along afterwards: 10% * Not participating: 0% Thanks to everyone for sharing how you’ll take part. Looking forward to a great Team 26!

Hi @Kristin Lyons thank you. I will be joining online too :)

Hi @David Berclaz _Apwide_What a great initiative! Could you please also add “Group” next to Communardo? The Communardo Group consists of the Atlassian Solution Partner Communardo (including its various locations) and the marketplace vendor Elevatic. Thank you!

Amazing milestone @Andy Gladstone ! Congrats! 

Thank you @Huwen Arnone _Deiser_Devoteam_ ! It's indeed an exciting milestone! :) 

Hey @Clara Vega _Simpleasyty_ Really appreciate how you framed this around friction rather than just AI capability, that resonates a lot. The point about “distance” is especially sharp. Most AI tools still feel like a context switch, and even small switches add up over a workday. If Rovo actually reduces that gap between…

Hi @Mehr_miniOrange Nice write-up — this is such a common pain point 👍 One angle that’s worth adding to this discussion is visibility into whether those licenses are actually needed in the first place. Viewtracker - Analytics for Confluence can help teams monitor real usage before deciding to buy more seats. For example,…