Elena_Elevatic Atlassian Partner

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,…

Hey @Himanshu Tiwary, This is a very well-articulated summary of the risks around Jira and JSM automation.The point about “testing only the perfect scenario” stands out in particular. Real-world variability is often where otherwise solid rules break down.Strong reminder that effective automation is less about complexity…

hi @Daria Kulikova_GitProtect_io Great overview! Especially the step-by-step approach. One thing I often see underestimated is security and compliance during migration. It’s usually not the migration itself that causes issues, but gaps around permissions, data handling, and recovery. There’s a helpful breakdown of common…

hey @Rob Hean Really great breakdown of labels! The pros/cons section especially resonates. The lack of governance and cleanup options has become a real pain point over time. One thing that’s helped in our case is complementing labels with more structured metadata and navigation. For example, using Metadata for Confluence…

Sounds great! Thank you!

Hey there! As usual, here you can find the results of our poll: 44% I recommend apps to decision-makers 22% I only use apps chosen by others 22% I decide which apps to purchase 11% I rarely use Marketplace apps It’s interesting to see that nearly half of you actively recommend apps, underscoring the influence your input…

Hi @Andreas Krupp _catworkx_ Thank you for putting together this list. It’s very helpful and covers many important aspects of the upcoming isolated cloud offering. From a marketplace partner point of view, I would add a few additional questions: * Will Atlassian provide technical guidelines for Marketplace Partners to make…

Hi @Kath Skerry It sounds like you’re looking for more robust reporting than Confluence’s built-in analytics. If your goal is monthly health reports at both the overall instance and per-space level, you might want to look into Viewtracker. Viewtracker is designed specifically for Confluence. It provides detailed insights…

Hi @David Nickell thank you so much! Your report is very helpful and interesting.

Hi @Rama K Goberu Thanks for the thoughtful comment. You raise some very valid points. You’re absolutely right that the conversation goes far beyond just Jira and Confluence. For many customers, the real complexity sits in the Marketplace ecosystem and the apps powering business-critical workflows. We’re hearing similar…

hi @Halina Cudakiewicz_Deviniti_ In my experience, lighter workflows with strong reporting tend to stick better. When approvals get too strict, people often just update things to get past the gate. If gaps are visible and easy to spot, teams usually fix them without being forced.

hey @C_Faysal _CFcon_ This is gold! Broken links are such a hidden headache after any Atlassian migration. Thank you for this article.

Super helpful! Love the clear, actionable automations, especially the stale page notifications and auto-archiving tips. Thank you @Rachel Morris 

hey @Mary from Planyway This is an incredibly thorough guide! I love how you not only break down the native Jira sprint report metrics but also highlight the gaps, like per-user visibility and time tracking. The visual examples and comparisons to other reports make it really easy to understand how to get actionable…

@Celina This is such a practical take! I totally agree that subtasks often become “micro to-do lists” that just clutter boards and reports. The litmus test you shared is perfect: different owners or deadlines = subtasks; single-person steps = checklist items. I also love the focus on smart checklists and automation —…

I totally agree with you @Dave Rosenlund _Trundl_ and Aaron: migrate less, design more. The shift from parity to fitness really stands out. Using migration as a forcing function to audit workflows, fields, and permissions can be uncomfortable, but that’s exactly where the real ROI appears. Leveraging AI like Rovo during…

Hi @Mahima_miniOrange Very good explanation! A lot of teams still evaluate Marketplace apps only by features and pricing, while architecture and data flow are what slow down approvals later. The Runs on Atlassian badge is becoming a real shortcut for security reviews because it answers the “where does the data live?”…

@Halina Cudakiewicz_Deviniti_ Thanks for this great perspective! The “truth gap” is real, especially in regulated or safety-critical environments. Keeping requirements as native Jira issues makes traceability part of the daily workflow instead of an afterthought. The key is finding enough structure for compliance without…

Hi @Natalia_Kovalchuk_SaaSJet_ Great breakdown! This goes beyond “exporting data” and actually shows how to measure process health. The reopen rate and due date shift metrics are especially practical for spotting workflow instability and planning discipline issues. Looking forward to the next analytics examples 👏

hi @Zoriana Bogutska_Kolekti Great guide!

Hey @Rob Hean This is such a clear breakdown. Thank you for putting this together! 👏 The comparison really shows why archiving should usually be the default in Confluence, with deletion reserved for true cleanup cases (duplicates, test pages, accidental uploads, etc.).

Congrats on bringing Time Metrics Tracker to Atlassian Government Cloud! 🎉

Hi @Iryna _Zhade Labs_ Meanwhile, we received some other responses, including yours, and the results have changed slightly. Here are the updated new results: * Microsoft 365: 42% * Slack/Teams: 17% * GitHub/GitLab: 17% * Google Workspace: 17% * Other (not specified): 8%

Hey @Zuzanna Patocka_Deviniti_ I like the context → routing → timing → visibility → execution approach. It makes prioritization a system thing, not just a “please hurry” request. In my experience, the biggest delays often come from tickets sitting idle, not because ownership is unclear, but because the assigned folks…

Thank you @Loren Siegel ! Amazing year and such a thoughtful recap! 🎉👏 Love the focus on deeper content, better events, and stronger Champion support. Huge thanks to all the CAB members for the time, care, and advocacy you put in for the community! 🙌💙🚀

Hey @Birkan Yildiz _OBSS_ This really resonates. Native history = editing safety. Baselines = audit safety. That distinction alone explains the value here. Super helpful explanation. Thank you!

Hi @Rishabh Kumar Shukla Thanks for clarifying your request. At the moment, I don’t have a specific framework or formal guidelines documented for governance and standardization to share. However, I recommend aligning with general best practices (architecture standards, security policies, and internal development…

Hi @Rishabh Kumar Shukla Thanks for your question. If you’re looking for a good starting point to build and govern Forge apps, the official Atlassian Forge documentation is the best guide to follow. It includes getting started steps, tutorials, and detailed how‑tos for building and deploying Forge apps. Best,Elena

Hi everyone! The results are in! Here is how the trust signals stacked up according to your replies: * 44% – Security & compliance certifications * 28% – Strong reviews & Marketplace ranking * 17% – Built or migrated to Forge * 11% – Other * 0% – Marketplace badges The Takeaway: Security and compliance are the runaway…

Hi @Tori Kaulins what an amazing quiz! I loved it. I find the result pretty much realistic.