Mia Tamm _Simpleasyty_ Atlassian Partner

Hey @Akankshya_M _Amoeboids_ one thing I’m finding increasingly important is the quality of the context behind the AI. Summaries and generated content are useful, but the really interesting use cases start when Jira and Confluence contain structured, consistent information that AI can reason over reliably. Otherwise you…

Hey @Doods Perea this is the part that interests me most. Once metadata becomes an input for AI, completeness and freshness stop being just governance concerns — they directly affect the quality of the answers. A graph can be perfectly connected and still propagate stale or inconsistent context. I’d love to see things like…

Hey @Monika Ambrozowicz_Seibert_ I think the tension between “metadata should be structured” and “pages should still feel like documents” is one of the more interesting Confluence problems. The part that gets especially challenging at scale is not displaying the fields, but keeping the structure consistent across hundreds…

Hi @Nico Chen This is a really interesting use case. Once you start treating Confluence as a content inventory, having the metadata in a consistent, structured form becomes almost as important as the page content itself. The native export is useful for migration/recovery, but not really designed as a human-friendly…

I think this is where Formula Fields become particularly interesting. The calculation itself is useful, but the bigger change is having reliable derived data that can then be reused consistently across reporting and decision-making. It will be interesting to see how teams start standardizing these formulas across projects…

The hierarchy point is a good one. I wonder if the bigger problem is not only color, but also how much context the sidebar tries to keep visible at the same time. Personally, I’d love to see Atlassian experiment with stronger collapsing/persistence behavior as well. The sidebar is great when it’s small, but gets…

Hi @Sven-Nils_Kossow , If you need the Excel file to remain connected to SharePoint, I think the SharePoint/OneDrive integration Fazila mentioned is probably the best approach. The permissions on the SharePoint side may also explain why embedding the whole file is currently failing. If you don't actually need a live…

Hi @Nathan Unsworth, If the native Content Properties Report continues to return only part of the results, there is an alternative you may want to try. Simple Tables can use Page Properties as a data source and display the collected information in a table where you can search, filter, sort, group and export the results.…

Nice example, @Prabhu Palanisamy _Onward_. I like the idea of bringing HiBob time-off data directly into the Service Collection flow instead of making people jump between tools. The API setup is useful, but the most interesting part for me is the workflow side — once that data is available in Jira, you can start making…

Really useful guide, @Andy LaHart. I like that you’ve treated accessibility as part of writing and structuring the content, not something to check at the very end. The examples around headings, link text and images are especially practical — small changes, but they can make a big difference to how usable a Confluence page…

This is a really good write-up, @Gabriela - LeanZero. The part about forge lint passing while the workflow condition could never actually run is probably the most useful takeaway for me. Those are exactly the bugs that are painful because everything looks valid until you test the real behaviour. I also liked the…

This is a really useful way of framing the problem, @Elena_Elevatic. The part that resonated most with me is the distinction between finding relevant documents and actually understanding how those documents relate to each other. A simple example: imagine someone asks, “What is our current approval process for enterprise…

Really interesting use case, @Darek Jaron - Appsvio I like the idea of bringing Salesforce cases and JSM requests into one place for the customer. From their point of view, they shouldn’t really have to care which system is handling the work behind the scenes. The unified portal approach makes a lot of sense. Nice example!

Very cool idea, @Jack Dillon - Pallas Apps. Bringing Python directly into Jira opens up a lot of interesting automation possibilities. Really nice to see this running on Atlassian too. Thanks for sharing!

Really useful distinction, @Birkan Yildiz _OBSS_ The difference between system-level audit logs and issue-level history is easy to blur, but it matters a lot once you need to answer “who changed what, and when?” across multiple work items. Clear explanation — thanks for sharing!

Great initiative, @Alex Ortiz I like that the focus isn’t just on “learning Rovo”, but on applying it to real Agile work and improving how teams actually o @Mandy Achter comment stood out to me too — “exactly the type of thing my teams need” is probably the best signal you can get for a session like this. I’d be especially…

Really interesting case study. Standardising 30+ projects without adding even more custom fields is probably the hardest part of this kind of setup. @Kate Pawlak _Appsvio_ made a great point too — the real win is when the solution actually fits the way the customer works instead of just adding another layer of process. The…

Hey @Prabhu Palanisamy _Onward_ Nice practical example. I like that you’ve included the field mapping and pagination details — those are usually the parts where an integration that looks simple on paper starts getting interesting. Also a good reminder that choosing the right identifier is key if you want the data in Assets…

Nice angle. Running entirely on Forge definitely removes a lot of the infrastructure questions that usually come with third-party apps. I also like that you still separate the platform security story from the actual app behaviour — where the data goes, what gets stored, and what permissions are really needed. That’s…

The “spider web” description is painfully accurate 😄 I agree with @Anne Saunders some workflows start with good intentions and slowly become impossible to navigate. And @Thorsten Letschert _Decadis AG_ makes a great point about resolution handling too. Those little configuration details are exactly the ones that become…

This looks really useful, especially for pages that already contain the full story but need to be presented to a different audience. One thing I’m curious about: if the original Confluence page changes later, is there any way to refresh the presentation from the updated content, or is the deck essentially a snapshot at the…

This title is painfully accurate @Maria Reisinger _MetaFrazo_ 😄 A dashboard can look perfectly healthy while the real story is hiding in the things that didn’t happen — reviews skipped, work stuck, ownership unclear. I like the idea of watching for those quieter signals instead of only celebrating throughput. Sometimes…

Really good point about separating priority from the assignment method. A critical incident and a routine request may live in the same Jira project, but treating them with the same routing logic can create very different problems. I also like the idea of defining the fallback explicitly. That’s often the part people only…

Really useful overview. I like how this brings the different pieces together instead of looking at each feature in isolation. The practical examples make it much easier to see where Rovo can actually help in day-to-day work. Thanks for sharing @Ajay _view26_!

Really interesting approach @MeghnaP_LogicLemur Labs. I particularly like the distinction between measuring how often an agent is used and whether people actually find its output useful. One thing I’d be curious about is how you account for “silent failure”. A user who gives negative feedback is relatively easy to measure,…

Welcome to the Community, @Joseph K_ Little 👋 You’ve definitely come to the right place — there’s a huge amount of practical knowledge here, especially around troubleshooting, cloud, networking, and all the interesting problems that appear when technology meets the real world. Looking forward to seeing you around the…

Hey @Jo-Lee Bertrand Simple Tables is free. 

Really interesting discussion. One approach I was thinking about while reading the replies is whether Page Properties could work as a lightweight governance layer here. For example, each governed page could include a small Page Properties block with fields such as Owner, Status, Last reviewed, Next review date and Expiry…

Really useful breakdown. I especially like the distinction between something that looks like a quote and something that is actually treated as one structurally. For quick notes, indentation is probably enough most of the time, but the semantic side becomes much more interesting once content starts being exported, reused,…

This is such a lovely idea 😊 Feel Good Fridays are one of those simple Community traditions that make the space feel much more human. I’d be happy to take one of the September or October dates if there’s still a spot available. I already have a couple of ideas that could be fun to share 😄 Thanks for keeping this going,…