Capable incident

Confluence Byline Entries Not Visible (Capable for Confluence)

Minor Resolved View vendor source →

Capable experienced a minor incident on November 13, 2025 affecting Capable Apps, lasting 3h 29m. The incident has been resolved; the full update timeline is below.

Started
Nov 13, 2025, 10:32 AM UTC
Resolved
Nov 13, 2025, 02:01 PM UTC
Duration
3h 29m
Detected by Pingoru
Nov 13, 2025, 10:32 AM UTC

Affected components

Capable Apps

Update timeline

  1. investigating Nov 13, 2025, 10:32 AM UTC

    Capable byline entries are not displaying on Confluence pages, which prevents users from accessing app features via the page header. This issue affects only the "Capable for Confluence" app and is limited to UI visibility - it does not impact the app's core functionality. We believe this stems from a broader Atlassian Forge platform issue affecting byline rendering across multiple apps, particularly when using Display Conditions that rely on App Properties - functionality Capable employs to let administrators hide specific capabilities.

  2. investigating Nov 13, 2025, 10:32 AM UTC

    We have escalated the issue to Atlassian. We will provide updates as soon as we have them.

  3. identified Nov 13, 2025, 12:39 PM UTC

    Atlassian has confirmed the issue stems from a recent change in their codebase, impacting Forge app byline rendering. They are now escalating this as a priority incident to their engineering team for a swift resolution. In parallel, the Capable team is deploying a targeted patch to the Capable for Confluence app. This workaround will restore byline functionality on our end, bypassing the Atlassian-side disruption. Expect the patch rollout within the next hour, followed by verification.

  4. resolved Nov 13, 2025, 02:01 PM UTC

    We have pushed a temporary workaround to restore page byline entries in Capable for Confluence. We will restore the global hiding feature once Atlassian have resolved the underlying issue.