Impact of adding system users (playbooks, boards) to a team for channel move in Mattermost

Troubleshooting
1

Hello,

I hope you’re doing well. I’m currently working with Mattermost (Version 9.7.3) and encountered an issue while moving a channel between teams. I would like to ask for your guidance regarding a potential concern after resolving the issue.

Summary
Added system users (playbooks, boards) to a team to successfully move a channel between teams in Mattermost 9.7.3.

Steps to reproduce

  1. Attempted to move a channel (customer-voice) from team-a to team-b using the command:

    mmctl --local channel move team-b team-a:customer-voice

    Received the following error:
    Error: unable to move channel "customer-voice": Unable to move a channel unless all its members are already members of the destination team.

  2. Investigated and found that the system users (playbooks and boards) were the only members of team-a not yet part of team-b.

  3. Added these system users to team-b using:

    mmctl --local team users add team-b-id playbooks@localhost playbooks
mmctl --local team users add team-b-id boards@localhost boards

  4. After adding the system users, I successfully moved the channel using the original move command.

Expected behavior
The channel move should not require adding system users (playbooks, boards) to the destination team.

Observed behavior
The system users had to be added to team-b to proceed with the channel move. I would like to know if keeping these system users in both teams has any potential impact on functionality or permissions.

Question
Does having playbooks and boards system users in both team-a and team-b affect the functionality or permissions of either team? Is it safe to keep them in both teams, or should they be removed after the move?

Environment Information

  • Mattermost Version: 9.7.3
  • Database Schema Version: 119
  • Build Number: 8851316927
  • Database: Postgres

Thank you in advance for your help! Any insights would be greatly appreciated.

2

9.7.3 is pretty old and EOL. If you have to stay on 9.7, I’d get to 9.7.6

https://docs.mattermost.com/about/mattermost-v9-changelog.html#release-v9-7-feature-release

This may be fixed in a newer version. I’d strongly suggest getting to 9.11

https://docs.mattermost.com/about/mattermost-server-releases.html

I don’t see this specifically mentioned in the changelog v9 changelog - Mattermost documentation

2 Likes
3

@john.oliver

Thank you for your feedback. You’re right that version 9.7.3 is old and has reached EOL. I appreciate the suggestion to upgrade to 9.7.6 or 9.11, and we will definitely consider it.

As we move forward with the upgrade, we’ll check if the issue is resolved in the newer versions. Your input is really helpful, and I’d appreciate any further advice you may have.

1 Like