Three GitLab steps work with issues. GitLab · Create an issue — Opens an issue in a project. GitLab · Update an issue — Closes or reopens an issue, or changes its title, description or labels. GitLab · Add a note — Comments on an issue or merge request.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the steps' settings but cannot change them.

Before you start

A GitLab connection with the api scope, whose user is a member of the project — see Connect GitLab.

Steps

Create an issue:

  1. Select + where the step should go. In the step picker, open Apps, select GitLab, then Create an issue. Or search GitLab.
  2. In Connection, choose your GitLab connection.
  3. In Project, choose the project — Projects the token reaches, as group/name. For example consulace/billing-service. The list reads Loading your projects… first.
  4. In Title, type the title.
  5. Optional: in Description — GitLab's Markdown.
  6. Optional: in Labels — Separate several with commas. Labels that do not exist yet are made. For example bug, billing.
  7. Optional: switch on Confidential so only project members with access to confidential issues see it. It is off unless you switch it on.
  8. Select Run this step to try it. This opens a real issue.

Update an issue:

  1. In the step picker, under GitLab, select Update an issue, and choose the Connection and Project.
  2. In Number, the issue's number in the project — The issue's or merge request's number — 42, #42 or !42.
  3. In State, choose Leave it, Close or Reopen.
  4. Fill in only what should change: Title, Description, Labels (Replaces its labels. Empty leaves them.).
  5. Select Run this step to try it.

Add a note:

  1. In the step picker, under GitLab, select Add a note, and choose the Connection and Project.
  2. In On, choose An issue or A merge request.
  3. In Number, its number — 42, #42 or !42.
  4. In Note, type the comment.
  5. Select Run this step to try it.

Output

Create an issue and Update an issue give the issue:

Field What it is
iid Its number in the project — what Update an issue and Add a note take.
id GitLab's id for it across the whole GitLab.
title, description Its title and description.
state opened or closed.
url The issue's page in GitLab.
author The username of whoever opened it.
labels A list of its labels.

Add a note gives the note's id and its body.

Good to know

  • Use iid, not id. The number people see in GitLab — #42 — is iid.
  • Update an issue changes issues only. To change a merge request, use the merge request steps — see Create or accept a GitLab merge request.
  • Each item runs the step once. Ten items open ten issues.

If something goes wrong

What you see Why What to do
Number is not an issue or merge request number. Number is not a whole number. Give a number such as 42, #42 or !42.
Project is empty when the step ran — an earlier step may not have given the value it names. Project came out empty. Choose the project.
GitLab refused: 404 Not found. (or 404 Project Not Found.) No issue or merge request with that number, or the token cannot see the project. Check the number, and that the token's user is a member of the project.
GitLab refused: 403 Forbidden. Check the connection's details on Connections. The token's user is not allowed to do this in the project. Give the user a higher role — see Connect GitLab.
GitLab refused: insufficient_scope. Check the connection's details on Connections. The token does not have the api scope. Make a token with api, then reconnect.
Could not load the projects GitLab did not give the list. "What you set here is kept." Select Try again, or Reconnect if offered.