Maksym Babenko_TypeSwitch_ Atlassian Partner

Hi André, Native public Confluence spaces can be useful for sharing documentation, but SEO indexing is not always easy to control or troubleshoot. I would check robots.txt, page-level indexing settings, canonical URLs, sitemap visibility, and whether Google Search Console reports the pages as crawled but not indexed. If…

Hi Lívia, If you want the entire space to be publicly accessible, you’ll likely need to check site-level anonymous access, space permissions, and any org-level restrictions that may override the space settings. But if your goal is to publish only selected Confluence pages publicly, you could also use a publishing app…

Hi Mark, Yes, this is possible. The simplest native option is Confluence Public Links, which allow specific pages to be shared without requiring users to log in. You need to enable public links at the site/space level, then enable the public link for the individual page. If you need a more polished customer facing version,…

Hi Merrill, Confluence public links are usually page-based, so child pages may still need to be enabled separately if you do not want to change the whole space permissions. One practical approach is to keep the space private and publish only the specific pages that should be externally accessible. If that is your use case,…

Hi Davy, This looks like Confluence generating temporary/blob image URLs for public page rendering. If bots rely on the image `src`, they may treat the same image as changed even when the actual attachment did not change. I would check whether the image is uploaded as a normal Confluence attachment and not pasted/embedded…

Hi James, This can happen when the page itself is shared publicly, but some content on it, such as diagrams, macros, or embedded elements, still requires authenticated Confluence access. I would first check page restrictions, space public link settings, and whether the diagram app/content supports anonymous viewing. As a…

Hi Haddon, If you mainly need the content to appear inside instance B, I don’t think Confluence Cloud has a clean native “include page from another instance” option. Since instance A is public, one practical workaround is to publish the source content as a clean external page and link to it from instance B, instead of…

Hi Jacolene, If these pages are client-facing, the cleanest solution may be to publish them outside the default Confluence public page view. Native public Confluence pages can still show some Confluence UI elements that are not ideal for customers. Our app Public Pages for Confluence may help here. It lets you publish…

Hi Jill, I would avoid opening a whole Confluence instance if only some pages need to be public. A safer pattern is to keep Confluence private and publish only selected pages that are meant for public access. Our app Public Pages for Confluence is built for this use case It lets you publish selected Confluence pages…

Hi Hendrik, For this case, I would be careful with publishing full page trees if some child pages should stay restricted. One option is to publish only selected pages instead of the whole hierarchy. This keeps sensitive or internal pages out of the public version. If that fits your use case, our app Public Pages for…

Hi Robert, I would first check for hidden formatting. Sometimes content copied from another page, Word, Google Docs, or an older Confluence editor keeps inline styles that affect font size. A quick test: copy the content into a plain text editor, then paste it into a new Confluence page and compare the rendering. If this…

Hi, This looks like an issue with Confluence’s native public link rendering rather than the page itself, especially if the HTML returns 200 but the browser still shows “Something went wrong”. I would first check whether the page contains macros, restricted content, or embedded elements that may still require authenticated…

Hi Oliver, Your approach makes sense. I would only be careful not to move or duplicate too much content into one public space. Another option is to keep the source pages in the existing team spaces and publish only the external facing pages. If public access outside Confluence is part of the goal, our app Public Pages for…

Hey Mark, the "Open to Anyone in this space" setting only controls access within your Confluence site. It does not make pages visible to unauthenticated users on the public web. That is a native Confluence limitation, not a configuration issue on your end. If you need pages to be genuinely public, check out Public Pages…

I’m the vendor of Public Pages for Confluence, so take this as a suggestion rather than a neutral recommendation. If your main need is to publish selected Confluence pages as a public knowledge base or documentation site, our app may be worth checking out. It is not a full Refined-style site builder, but it focuses on…

Yes, quite a few teams still use Confluence as the authoring layer for customer documentation. It works well for collaboration, but the publishing experience often needs extra help if you want something that feels more polished for end users. In practice, many teams keep Confluence as the source of truth and add a separate…

Yes, definitely. A lot of teams use Confluence as the content source for customer facing help centers and knowledge bases. The main limitation is usually the public experience, branding, and SEO side. If you want a lighter setup for publishing selected pages publicly, Public Pages for Confluence could be worth a look.

If you only need to share specific pages, I would avoid making the whole space public. A page level approach is usually safer because it limits exposure to only the content you want to share. If you need a cleaner public setup for selected pages, apps like Public Pages for Confluence can help with that.

This usually points to DNS propagation or caching. I would first verify the CNAME target, wait for propagation to complete, and test in an incognito window or another network. If this is for publishing Confluence content publicly, I’ve seen similar confusion happen when switching domains, so it is worth double checking…

If public sharing is acceptable, another option is to publish just that one page externally instead of granting Confluence access to the whole space. Public Pages for Confluence for this exact use case sharing specific pages publicly without opening the whole space.

For teams that need something more customer-facing for example public documentation, branded pages, or SEO-indexable content discoverable through Google we recently launched Public Pages for Confluence. It’s a different use case, but it can be helpful when Confluence content needs to work more like a public website than a…

Hello Bud, this discrepancy between Sprint Report and Burnup Chart is a classic Jira quirk. Usually it happens because: The Sprint Report only includes issues assigned to the sprint at closure The Burnup Chart shows total scope over time, including issues added mid-sprint or removed later That’s why you’re seeing 35 vs 46…

Hey @Tyler Cassar This sounds like a classic case where automation starts to hit its limits, especially with conditional logic and branching. If you're open to trying an app, you might find Risk Radar helpful. It’s a lightweight tool that lets you assign risk levels (e.g., High/Medium/Low) and automatically calculates a…

Hey @Chris Peake, I’ve faced a similar challenge before — Jira's built-in reports often struggle with showing status snapshots over time (like “how many issues were Blocked at the end of each week”). If you’re open to apps, Issue Delivery Report might help. It reads the full issue history and categorizes time spent in each…

Hey @Mayur Gaikwad/Tech PMO I had the same need on our team, especially for analyzing how long issues spend in each status and when transitions happen. You might want to check out Issue Delivery Report — it’s a Jira Cloud app that uses the full changelog to: Show when each status transition happened Calculate exact time…

Hi @Claire Abt ! We ran into a similar problem on our team — especially with issues bouncing in and out of statuses like “Input Required” or “Waiting for Review.” We’ve been using an app called Issue Delivery Report for Jira — it automatically tracks how much time each issue spends in each status based on the full…

Hi @Raunak Maskay We had a similar challenge in our team with internal SLAs inside Jira Software (not JSM). You might want to try the Issue Delivery Report app it’s a lightweight tool that shows: Time spent in each status Total turnaround time Flow Efficiency Late sprint additions and warnings if flow is inefficient It…

Thanks, Bill, will do!

Hi @Rostam Kilgour! I’m part of the team behind Flow Time Report, a Jira Cloud app that tracks how long each issue stays in every status, including how long it remained unassigned or in "To Do" before being picked up. It’s a simple way to get this visibility without setting up custom automations or reports. ➡️…

Hi @Khai Ha I’m part of the team behind Flow Time Report, a Jira Cloud app we built to track time spent in each status automatically, no need to create complex automations. It shows the full time-in-status history right inside each issue, with visual indicators like On Track, At Risk, and Overdue. ➡️…