Suptask
Suptask Web AppSignup for FREE
  • Welcome
  • Getting Started
    • Install Suptask
      • Slack permission scopes
      • Invite the Suptask App
    • Your first Inbox & Form
    • Ticket submission
    • Manage and Reply on tickets
    • Key concepts
    • User Guides
      • Ticketing as an Agent
      • Ticketing as a User
      • Rollout and Onboarding guide
    • FAQ & Troubleshooting
    • Contact Support
    • Videos
  • Setup & Configure
    • Inboxes
      • Inboxes
      • Users and Agents in the same channel
      • Service Level Agreements (SLA)
      • Agent Work Hours
      • Automatically create tickets from new messages
      • Migrate to the new generation
    • Forms & Fields
      • Forms
      • Custom Fields
      • Default Fields
      • Custom Statuses
      • Tags
      • Using the Organization field
    • Users & Permissions
    • Slack External Connections
    • Multiple Slack Workspaces
      • Multiple Workspaces & Slack Community
      • Enterprise Grid
    • Branding & White-labeling
    • Language & Translations
  • Working with tickets
    • For Agents: who respond and manage tickets
      • Overview and manage tickets as an Agent
      • Responding to tickets
      • Move or Escalate to another Inbox
      • Submit tickets on behalf of a user
      • Request and manage Approvals
      • Customer Satisfaction Score (CSAT)
      • Templated answers with Canned Replies
      • AI Assistant
      • Followers
      • Delete tickets
    • For Users: who submit tickets
      • How to submit a ticket
      • Overview your tickets as a user
    • Overview & Analytics
      • Overview and track tickets
      • Dashboard
      • Reports
    • Essentials for Your daily work
      • Tickets Summary Notifications
      • Setup one-click emoji reactions
      • How to search for tickets
      • Display Suptask in Slack
  • Integrations, Automations & Workflows
    • Introduction to Integrations
    • List of integrations
    • Integration guides
      • Slack Workflows
      • WhatsApp
      • JIRA Software
      • Zendesk
      • ClickUp
      • Notion
      • Google Sheets
      • Suptask API
      • WebHooks
      • Export API
      • Integrate with other Slack Apps
      • External issue & ticketing systems
        • Create tickets from Suptask to GitLab
        • Create tickets from Suptask to GitHub
        • Create tickets from Suptask to JIRA
    • Email-to-Slack Ticketing
      • Email-to-Slack Ticketing
      • Gmail & Google Workspaces
      • Microsoft Outlook
      • AI Email routing
    • On-call rotation
    • Automations in Suptask
  • Account Management
    • Account Settings
    • Subscription & Billing
      • Subscription & Billing
      • Integrations billing
      • Limitations in the Free plan
Powered by GitBook
On this page
  • Overview
  • Prerequisites
  • Set up the GitLab integration
  • Using the GitLab integration with Suptask

Was this helpful?

Export as PDF
  1. Integrations, Automations & Workflows
  2. Integration guides
  3. External issue & ticketing systems

Create tickets from Suptask to GitLab

Learn how to set up the integration with GitLab

PreviousExternal issue & ticketing systemsNextCreate tickets from Suptask to GitHub

Last updated 6 months ago

Was this helpful?

Overview

The Suptask integration with GitLab enables you to escalate tickets directly from Slack to GitLab. With a single reaction emoji (the :tornado: 🌪️) you'll be able to create tickets to your choice of repositories, directly from a Suptask ticket in Slack.


Prerequisites

  1. The account name of your GitLab account. Can either be an organization or personal account. In this example the account name is acme.inc, the repository is core (case-sensitive) and the server is https://gitlab.comExample: https://gitlab.com/acme.inc/core

  2. Create an access token for your user account in GitLab. You can find it from your user profile or by navigating to your user account > Preferences > Access tokens. Access tokens can also be created for Projects. In such a case, make sure the Role is set to minimum Developer. The minimum Scope for the token needs to be the following: apiStore the token once you have it. You will need it when configuring the integration within Suptask.


Set up the GitLab integration

  1. Navigate to the in your Account.

  2. Press on +GitLab button to create a new Gitlab integration.

  3. Give it a name and specify what Suptask ticket forms to enable the integration for. Tickets initiated through forms are then enabled with the trigger to create a ticket within the integration system (in this case GitLab).

  4. Next you will need to create credentials for your integration. Credentials can be shared across several integrations of the same type. Here you will need your GitLab server URL and the Access token that you stored from your Gitlab account.

  5. Proceed to the next step and enter the GitLab account name that you collected from the preparation step.

  6. Specify what repositories in GitLab you want to enable the integration for. Make sure you enter the exact name, case sensitive. If you enter the incorrect name, the integration connection will not work.

  7. Finally specify if you want to add any default GitLab labels to the tickets that are created from Suptask.

  8. Done! The integration is now activated.


Using the GitLab integration with Suptask

  1. Make sure you are within the Responder channel of your Inbox.

  2. On one of the received tickets in the channel, add the :tornado: 🌪️ reaction emoji to the ticket message in the channel. See below for a sample screenshot.

  3. This will trigger a selection where you can specify to what integration target you want to send the new ticket, the same as configured in the previous step.

  4. From here you will be able to edit the Description and Title of the issue sent to Gitlab. The Description field is pre-populated with a default template which you can edit according to your needs. Use the Suptask ticket placeholders to include Suptask ticket information automatically into the Gitlab issue. Especially the ticketUrl placeholder is valuable as it takes you directly to the Suptask ticket in Slack as a reference.

After creating a related ticket in GitLab, the ticket message thread in Slack will receive the GitLab issue url, linking the both tickets together.

Gitlab supports quick actions which can help you perform further actions by entering these directly at the end of the Description field. This allows you to for example set specific labels for the created issue. Read more Example screenshot on adding the the :tornado: 🌪️ to a ticket message in the responder channel:

Integrations page
here