Mia Tamm _Simpleasyty_ Atlassian Partner

Hey @Ananjan_miniOrange This is such an important distinction: giving someone access is relatively easy, but being able to confidently explain what they can access and why is a completely different challenge. Guest access is a great starting point, but I really like the reminder that permissions can evolve over time as…

Really useful perspective, @Tuncay Senturk _Snapbytes_, I liked the distinction between an issue being “Done” and the release actually being ready. Evidence, permissions, and consistency can tell a very different story. The idea of using attachments as supporting evidence, without making them the whole process, feels like…

Thanks again for explaining the workflow, @Jo-Lee Bertrand The more I think about your use case, the more I wonder whether there may be a more powerful way of structuring this than relying entirely on Task Report. This is actually very close to an integration we're currently finalising between Simple Tables and Confluence…

Really useful reminder, @Karl from RicksoftThe distinction between a field being hidden in a particular view and the data actually being protected is an important one and probably very easy to overlook as request forms evolve over time. I especially liked the suggestion to test both the customer portal and the agent side…

Hi @Jo-Lee Bertrand that definitely sounds like something that may have changed on the Confluence side if it stopped working across multiple spaces at exactly the same time. Out of curiosity, are you mainly using the Task Report to: * find tasks contained in pages with a specific label, or * use the page label itself as…

Such a lovely thread @Kristján Geir Mathiesen I really enjoyed the story about Thor; it’s amazing how a few words from the right person, at the right moment, can stay with us for years. One I come back to quite often is “Perfect is the enemy of good.” It’s a nice reminder to keep moving, especially when you’re tempted to…

Really interesting post @Thorsten Letschert _Decadis AG_. What I liked most is that the AI is helping inside the existing workflow rather than trying to replace it. Keeping validation and user control in the process makes the feature feel much more useful and trustworthy. Also appreciated the engineering lessons at the end…

Hi @Birkan Yildiz _OBSS_ What I liked most here is actually the modelling decision behind the solution. It’s very tempting to create another custom field every time someone asks a new question: time in review, time waiting for a customer, time to first response, time between two specific statuses… and suddenly the…

This is a great reminder that an “SLA” is rarely just one timer. Once you have several clients, different support tiers, working hours, time zones and contractual commitments, the real challenge is making all of that complexity disappear for the person actually handling the ticket. That’s probably what I liked most about…

Really interesting update @Elena_Elevatic. One of the hardest parts of a Data Center → Cloud migration is often not moving the content itself, but preserving all the structure and conventions teams have built around that content over the years. That’s why the automatic conversion into Content Categories stood out to me.…

This is an incredible amount of work to put into a Community post. Thank you for taking the time to document all of this. What I really appreciate is that you didn’t stop at explaining the idea or showing the final result. You actually walk through the whole process: the initial setup, how the different pieces fit…

Really nice example, @Laura Marin - Millarum. Cross-project dependencies are one of those things that feel manageable until a release starts touching several teams and tech stacks at once. I especially liked the separation between the Bundle Release for coordination and the roadmap for the higher-level view. It keeps the…

Really useful breakdown, especially because webhooks often look simple until you start relying on them for something important in production. The points around delivery visibility and retries really stood out to me. When something fails silently, debugging quickly becomes much harder than the original integration itself. I…

Nice update. I think this is one of those small settings that can actually make a pretty big difference. Most people probably won’t touch permissions after creating a goal or project, so getting the default right matters a lot. I also like that this only affects new items and doesn’t suddenly change how existing goals and…

Nice addition. What I particularly like here is that you’ve gone beyond “here are some endpoints” and included the less glamorous parts that usually decide whether an integration works well in production: permissions, pagination, retries, workflow triggers, and data ownership. One thing I’d be curious about as usage grows:…

Really interesting way to look at reopened issues, especially treating them as a pattern rather than just another status change. One thing I’d add is that the transition path may be even more revealing than the reopen count itself. An issue that repeatedly goes Done → Reopened → In Progress → Done is telling a very…

Okay, I came here thinking this was a simple ice cream question and now I have a problem 😂 @Mikael Sandberg bringing cookie dough into the discussion is already playing dirty. That’s almost impossible to argue against. I appreciate the classic approach, sometimes you don’t need twenty toppings and a strategy meeting to…

Hi @Prabhu Palanisamy _Onward_ nice example of connecting external device data into Jira Assets. One thing I’d be interested in is how you handle changes over time. For example, if a device is renamed, reassigned, or removed in Workspace ONE, does the integration update the existing Asset object reliably, or is there any…

@Yana Misiura_BrizoIT interesting use case. I like the idea of treating a calendar as more than just a place for dates, and instead using it as a shared operational view of work and resources. The resource-planning example is especially useful because that kind of information often ends up scattered across Jira issues,…

@Elle Ky Nice improvement. Table sizing is one of those small things that can make a surprisingly big difference when working with larger datasets in Confluence. I especially like having both options: letting Confluence fit the table to the content automatically, while still keeping manual control when a specific layout is…

Hi @Yuta_MiddleCore_ really interesting approach. I especially like the idea of treating each “ask” as a clearly defined section instead of trying to solve everything with one large prompt. The reviewable draft step also feels important. Keeping the generated content visible and easy to validate before it becomes part of…

Hi @Ricardo, This is a really interesting problem, especially the distinction between detecting a contradiction and governing what happens after it has been identified. I wonder if part of the answer could be making the decision itself structured metadata on the page, for example: * Authority status: Authoritative /…

Hi @Ryan J, Out of curiosity, what are you using these database tags to represent? Are they mainly statuses like Completed / Not Completed, or do you use colors to distinguish things like categories, permissions, priorities or other metadata? I’m asking because it sounds like the color itself is an important part of how…

Hi @Chris, Reading the discussion, I think Confluence Databases are definitely worth testing first, especially if you want each feature to become a structured record managed directly in Confluence. There is one other distinction I would consider before rebuilding everything, though: Are those 30–50 values really page…

Hi @Kasyah Sydnor, One additional approach you may want to consider is keeping each policy as a regular Confluence page and using the native Page Properties macro for the metadata you listed. For example, every policy page could contain: * Document ID * Category * Type * Current Version * Status * Owner * Approved By *…

Hi @Stephen Ellwood, the issue you describe seems to happen when another macro has to process the rendered Page Properties Report output instead of reading the underlying Page Properties data. That creates a fragile hand-off between macros, especially for operations that expect plain values. I work on Simple Tables at…

Thanks @Veronika Chachkova I Stiltsoft I completely agree with one thing you mentioned: the page should remain the primary source of truth. That's actually one of the reasons I wanted to write this article. I think many teams naturally end up storing structured metadata inside pages because the context lives there as well.…

Thank you @Anwesha Pan 

Hi @anna_kiviharju, Thanks for sharing the screenshots. Before digging deeper into whether this is related to native tables, Databases, or a recent Confluence change, could you share a bit more about what you’re trying to achieve with these tables? For example: * Are these tables mainly used for reporting, documentation,…

Great point, @Stavros_Rougas_EasyApps The way “Runs on Atlassian” isolates customer data indeed changes the conversation. It’s security by design. SOC2 still adds trust from a business and process standpoint, but the combination of both gives customers real peace of mind.