Skip to content
GitLab Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #25269
Closed (moved) (moved)
Open
Created Dec 02, 2016 by Mark Pundsack@markpundsackContributor

Allow Mattermost team creation when enabling Mattermost Command

Resources

PM @victorwu

Description

When using Omnibus installation with Mattermost, we are going to have a flow to automatically add the Slash Integration to Mattermost (#24769 (closed)). While this flow shortens the time from configuration to usage, we should also cover the case when there are no teams or when the user has to create a new team. This will speed up the idea-to-production workflow setup even more.

Proposal

During the installation flow of the slash commands service for Omnibus-Mattermost, let users pick an existing team or create a new team. Mattermost may restrict who can create teams, so we need to handle the error case.

Specific details of the different scenarios are noted in the design specs:

🔍 Check design specs (for spacing, sizes, colors and text copying) — Hide the notes using the control in the top-right corner

For users that can create Mattermost teams (Mattermost system admins or regular users if they have permission)

One or more teams already available No teams available
1) Select or create team image 2) New team image image

For users that can't create Mattermost teams

One team available Two or more teams available
image image

For users that can't create Mattermost teams nor manage integrations: display the “no permission” screen developed in #24769 (closed)

The Command trigger word field is pre-filled with the project slug. When creating teams, the team Name and URL fields are pre-filled with the group name and group slug, respectively. The users can naturally change those fields, but we take the lead and fill those for them.

Links

  • Was from #23964 (closed)
  • Builds on #24769 (closed)
Assignee
Assign to
Time tracking