Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playbooks v1 vs v2 clarifications #7394

Merged
merged 2 commits into from
Sep 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions source/guides/repeatable-processes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,10 @@ Build repeatable processes
.. include:: ../_static/badges/ent-cloud-selfhosted.rst
:start-after: :nosearch:

.. important::

Mattermost v10 introduces Playbooks v2 for all Enterprise licensed customers. New Playbooks features & security updates will only be added to Playbooks v2 moving forward; however, Playbooks v1 will be maintained for Team Edition and Professional instances running :doc:`supported v9.x Mattermost server releases </about/mattermost-server-releases>`.

Use collaborative playbooks in Mattermost to provide structure, monitoring and automation for repeatable, team-based processes integrated with the Mattermost platform. Playbooks are :doc:`configurable checklists </repeatable-processes/work-with-tasks>` for teams to achieve :doc:`specific and predictable outcomes </repeatable-processes/metrics-and-goals>`, such as incident response, software release management, and logistical operations.

Playbooks monitor channels for keywords or user actions to trigger a structured process, which brings up a set of individual or shared tasks, each associated with manual or automated actions. As playbooks are executed, some may have requirements for :doc:`broadcasting status updates to stakeholders </repeatable-processes/notifications-and-updates>` at regular intervals, to populate workflow dashboards by conducting :ref:`retrospectives <repeatable-processes/metrics-and-goals:configure retrospectives before a run>` after the core process is complete, or other customer requirements as exit criteria for a :doc:`playbook “run” </repeatable-processes/work-with-runs>`.
Expand Down
Loading