Skip to content

MM-67771: Update Report a Problem default behavior docs#8845

Open
vish9812 wants to merge 3 commits intomasterfrom
MM-67771-report-a-problem-docs
Open

MM-67771: Update Report a Problem default behavior docs#8845
vish9812 wants to merge 3 commits intomasterfrom
MM-67771-report-a-problem-docs

Conversation

@vish9812
Copy link
Copy Markdown
Contributor

@vish9812 vish9812 commented Apr 1, 2026

Summary

  • Update "Default link" description for Report a Problem: licensed servers now open an email to Mattermost support (instead of the Support Portal URL), and free edition directs to troubleshooting forums (instead of GitHub issues)
  • Fix typo in MM_SUPPORTSETTINGS_REPORTAPROBLMEMAILMM_SUPPORTSETTINGS_REPORTAPROBLEMMAIL

Web PR: mattermost/mattermost#35900
Mobile PR: mattermost/mattermost-mobile#9703

Test plan

  • Verify the rendered docs accurately describe the new default behavior for licensed and free edition

🤖 Generated with Claude Code

Update the "Default link" description to reflect the new behavior:
licensed servers now open an email to Mattermost support, and free
edition directs to the troubleshooting forums.

Also fix typo in REPORTAPROBLMEMAIL env var name.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 1, 2026

📝 Walkthrough

Walkthrough

Updated documentation for the "Report a Problem" site configuration setting: clarified the Default behavior to state licensed deployments open a support case by email to Mattermost support, unlicensed/community deployments are directed to troubleshooting forums, and fixed a typo in the environment variable name from MM_SUPPORTSETTINGS_REPORTAPROBLMEMAIL to MM_SUPPORTSETTINGS_REPORTAPROBLEMMAIL.

Changes

Cohort / File(s) Summary
Documentation
source/administration-guide/configure/site-configuration-settings.rst
Rewrote "Report a Problem" default behavior to indicate licensed deployments open a support case by email to Mattermost support and unlicensed/community deployments go to troubleshooting forums; corrected environment variable name from MM_SUPPORTSETTINGS_REPORTAPROBLMEMAIL to MM_SUPPORTSETTINGS_REPORTAPROBLEMMAIL in metadata and table row.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately reflects the main change: updating Report a Problem default behavior documentation with reference to the related ticket MM-67771.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The pull request description is directly related to the changeset, describing both the documentation updates and the typo fix included in the changes.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch MM-67771-report-a-problem-docs

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 1, 2026

Newest code from mattermost has been published to preview environment for Git SHA 4a5b018

@vish9812 vish9812 requested a review from esethna April 1, 2026 17:07
@vish9812 vish9812 self-assigned this Apr 1, 2026
@vish9812 vish9812 added 1: PM Review Requires review by a product manager 2: Editor Review Requires review by an editor and removed 1: PM Review Requires review by a product manager labels Apr 1, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 1, 2026

Newest code from mattermost has been published to preview environment for Git SHA 4a5b018

@esethna
Copy link
Copy Markdown
Contributor

esethna commented Apr 13, 2026

@vish9812 please rebase to the v11.7 (if that's correct?) branch when it's cut in the next few days

@esethna esethna added Do Not Merge/Awaiting Next Release To be merged with the next release (e.g. API documentation updates) and removed 2: Editor Review Requires review by an editor labels Apr 13, 2026
@esethna esethna added this to the v11.7.0 milestone Apr 13, 2026
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
source/administration-guide/configure/site-configuration-settings.rst (1)

256-256: Consider using consistent terminology.

The description uses "Customers with a Mattermost license" and "Unlicensed Mattermost deployments". For consistency with terminology used elsewhere in this documentation (e.g., "licensed deployments" and "unlicensed deployments"), consider standardising the phrasing.

♻️ Suggested terminology alignment
-- **Default**: Customers with a Mattermost license can open a support case by email with the Mattermost support team. Unlicensed Mattermost deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.
+- **Default**: Licensed deployments can open a support case by email with the Mattermost support team. Unlicensed deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@source/administration-guide/configure/site-configuration-settings.rst` at
line 256, Update the phrasing in the sentence that currently reads "Customers
with a Mattermost license" and "Unlicensed Mattermost deployments" to use
consistent terminology used elsewhere (e.g., change to "licensed deployments"
and "unlicensed deployments"); locate the sentence in
site-configuration-settings.rst (the Default: line) and replace the first clause
with "licensed deployments" so the full sentence uses "licensed deployments can
open a support case by email with the Mattermost support team. Unlicensed
deployments are directed to the troubleshooting forums..." to match existing
docs terminology.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@source/administration-guide/configure/site-configuration-settings.rst`:
- Line 256: Update the phrasing in the sentence that currently reads "Customers
with a Mattermost license" and "Unlicensed Mattermost deployments" to use
consistent terminology used elsewhere (e.g., change to "licensed deployments"
and "unlicensed deployments"); locate the sentence in
site-configuration-settings.rst (the Default: line) and replace the first clause
with "licensed deployments" so the full sentence uses "licensed deployments can
open a support case by email with the Mattermost support team. Unlicensed
deployments are directed to the troubleshooting forums..." to match existing
docs terminology.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d17d8fe-316e-4201-aa65-e086cf7a4650

📥 Commits

Reviewing files that changed from the base of the PR and between 4a5b018 and d1c2e7c.

📒 Files selected for processing (1)
  • source/administration-guide/configure/site-configuration-settings.rst

@github-actions
Copy link
Copy Markdown
Contributor

Newest code from mattermost has been published to preview environment for Git SHA d1c2e7c

@Combs7th
Copy link
Copy Markdown
Contributor

@vish9812 - Can you help rebase to the 11.7 documentation branch when you're able? Thanks so much in advance!

Copilot AI review requested due to automatic review settings April 24, 2026 04:14
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
source/administration-guide/configure/site-configuration-settings.rst (1)

256-256: Consider clarifying the "open a support case by email" mechanism.

The phrase "can open a support case by email with the Mattermost support team" could be more specific about what actually happens when a licensed user selects Report a Problem. Based on the PR description mentioning "open an email," it appears an email client opens automatically. Consider revising to be more explicit:

Suggested clarification
-- **Default**: Customers with a Mattermost license can open a support case by email with the Mattermost support team. Unlicensed Mattermost deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.
+- **Default**: Licensed Mattermost deployments open an email in the user's default email client addressed to Mattermost support. Unlicensed Mattermost deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.

This helps Novice Nate (a novice IT admin) understand exactly what users will experience when they select this option.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@source/administration-guide/configure/site-configuration-settings.rst` at
line 256, Update the Default description sentence that currently reads "can open
a support case by email by email with the Mattermost support team" to explicitly
describe the user experience when a licensed user selects "Report a Problem"
(e.g., that it opens the user's default email client with a prepopulated message
addressed to Mattermost support). Locate the sentence containing the "Default"
text and the phrase "Report a Problem"/"open a support case by email" and
replace it with a clearer line that states the email client will open and what
fields (recipient/subject/body) are prefilled or that the user is taken to an
email compose window to send to Mattermost support.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@source/administration-guide/configure/site-configuration-settings.rst`:
- Line 256: Update the Default description sentence that currently reads "can
open a support case by email by email with the Mattermost support team" to
explicitly describe the user experience when a licensed user selects "Report a
Problem" (e.g., that it opens the user's default email client with a
prepopulated message addressed to Mattermost support). Locate the sentence
containing the "Default" text and the phrase "Report a Problem"/"open a support
case by email" and replace it with a clearer line that states the email client
will open and what fields (recipient/subject/body) are prefilled or that the
user is taken to an email compose window to send to Mattermost support.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 49af6177-5b0d-44c4-805d-5f97268c5e57

📥 Commits

Reviewing files that changed from the base of the PR and between d1c2e7c and 9999eb3.

📒 Files selected for processing (1)
  • source/administration-guide/configure/site-configuration-settings.rst

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates Mattermost documentation for the Report a Problem setting to reflect new default behavior and corrects a related environment variable typo.

Changes:

  • Update the “Default” behavior description for Report a Problem for licensed vs. unlicensed deployments.
  • Fix environment variable name typo for ReportAProblemMail.

With self-hosted deployments, you can specify how the **Report a Problem** option behaves in the Mattermost app via the **Help** menu:

- **Default link**: Uses the default Mattermost URL to report a problem. Customers with a Mattermost subscription are directed to the `Mattermost Support Portal <https://support.mattermost.com/hc/en-us/requests/new>`_. Community deployments are directed to `create a new issue on the Mattermost GitHub repository <https://github.com/mattermost/mattermost/issues/new>`_.
- **Default**: Customers with a Mattermost license can open a support case by email with the Mattermost support team. Unlicensed Mattermost deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Editor Evie, Friction) In the type list, the label changed from Default link to Default. Unless the System Console option label also changed, this makes the docs harder to match/search against the UI. Also, “open a support case by email” is a bit ambiguous—consider wording that explicitly says it opens the user’s default email client/composer to contact Mattermost Support (and that unlicensed deployments are directed to the troubleshooting forums).

Suggested change
- **Default**: Customers with a Mattermost license can open a support case by email with the Mattermost support team. Unlicensed Mattermost deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.
- **Default link**: Customers with a Mattermost license can open their default email client or composer to contact Mattermost Support. Unlicensed Mattermost deployments are directed to the `troubleshooting forums <https://mattermost.com/pl/report_a_problem_unlicensed>`_.

Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown
Contributor

Newest code from mattermost has been published to preview environment for Git SHA 9999eb3

@vish9812
Copy link
Copy Markdown
Contributor Author

@esethna @Combs7th Do you want to me raise this PR against v11.7 branch instead of master?
Or does @amyblais merges master into v11.7 later?

@amyblais amyblais removed this from the v11.7.0 milestone Apr 24, 2026
@amyblais
Copy link
Copy Markdown
Member

amyblais commented Apr 24, 2026

Do you want to me raise this PR against v11.7 branch instead of master? Or does amyblais merges master into v11.7 later?

@vish9812 The server PR hasn't been merged yet so we don't yet know which release this will go into. For now we can keep the "Do not Merge" label and update the milestone after the server PR has been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Merge/Awaiting Next Release To be merged with the next release (e.g. API documentation updates)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants