Skip to content

[Feature Request]: Subscribe or receive notification on known issues page updates #3401

@theletterf

Description

@theletterf

Additional Context

Customer request highlighted in internal feedback: Teams experiencing frequent bugs and using specific versions wish for proactive notifications, not just updates at planned upgrades. This is related to upcoming changes in release notes and was discussed but is not on the roadmap yet. See Slack thread for details.

Alternative Solutions

Currently, users must manually check the known issues page for updates; this is not scalable or proactive and can lead to missed important issues, especially for customers dealing with unstable or bug-prone configurations. There are no alternatives for doc-specific subscription currently available.

Examples and Research

  • Many documentation systems (e.g., Read the Docs, Confluence) provide a "watch" or "subscribe" feature for specific pages or sections.
  • RSS/Atom feeds are a common way to enable subscriptions to page updates.
  • Enabling such a feature for https://www.elastic.co/docs/release-notes/elasticsearch/known-issues would address direct customer requests.

How important is this feature to you?

"Important"

What problem are you trying to solve?

Currently, there is no way for customers to subscribe to updates or receive notifications when new known issues are uncovered in the documentation (for example, https://www.elastic.co/docs/release-notes/elasticsearch/known-issues). Customers with many issues, especially on specific versions, want to proactively know when something new is discovered rather than only finding out when they come back to review the list during a planned upgrade.

Proposed Solution

Implement a mechanism in docs-builder to enable subscription (e.g., email or reminder) to changes or new entries in known issues pages across the docs. Ideally, this would allow users to receive notifications when these pages are updated, either as a native feature, integration with an external service, or even RSS/Atom feeds. This could be generalized for other important doc pages in future.

Prerequisites

false,false

View original Slack conversation

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions