Qase

<a href="https://about.gitlab.com/" rel="nofollow noopener noreferrer" target="_blank">GitLab</a> is a web-based DevOps lifecycle tool that provides a Git repository manager providing wiki, issue-tracking, and CI/CD pipeline features.

With Qase’s GitLab integration, you can:

Link your GitLab issues to Qase <a href="https://docs.qase.io/en/articles/5563704-test-cases">test cases</a>, <a href="https://docs.qase.io/en/articles/5563702-test-runs">test runs</a>, <a href="https://docs.qase.io/en/articles/5563710-defects">defects</a>

Create a new issue in GitLab when you file a <a href="https://docs.qase.io/en/articles/5563710-defects">defect</a> during a test run in Qase and their statuses are automatically synchronized, in both directions. [Qase &lt;&gt; GitLab]

Trigger your GitLab automated pipeline directly from Qase.

- Link your GitLab issues to Qase <a href="https://docs.qase.io/en/articles/5563704-test-cases">test cases</a>, <a href="https://docs.qase.io/en/articles/5563702-test-runs">test runs</a>, <a href="https://docs.qase.io/en/articles/5563710-defects">defects</a>
- Create a new issue in GitLab when you file a <a href="https://docs.qase.io/en/articles/5563710-defects">defect</a> during a test run in Qase and their statuses are automatically synchronized, in both directions. [Qase &lt;&gt; GitLab]
- Trigger your GitLab automated pipeline directly from Qase.

For installation, you will require <code>GitLab URL</code> and the <code>Access token</code>.

Firstly, sign-in to your GitLab account and navigate to the <code>Preferences</code> from the profile menu:

The GitLab profile menu with Preferences selected

Go to the <code>Access tokens</code> page:

The Access tokens page in GitLab user settings

To create a new <code>Personal Access Token</code>, select the scope <code>api</code> and click on the Create Personal Access token:

Creating a personal access token in GitLab with the api scope selected

On Qase, navigate to the <a href="https://app.qase.io/apps" rel="nofollow noopener noreferrer" target="_blank">Apps</a> section, find the GitLab app and click <code>Install now</code>.

The GitLab app card on the Qase Apps page, with its Install now button

1. Firstly, sign-in to your GitLab account and navigate to the <code>Preferences</code> from the profile menu:
 The GitLab profile menu with Preferences selected
 ​
2. Go to the <code>Access tokens</code> page:
 The Access tokens page in GitLab user settings
 ​
3. To create a new <code>Personal Access Token</code>, select the scope <code>api</code> and click on the Create Personal Access token:
 Creating a personal access token in GitLab with the api scope selected
 ​
4. Copy your token to clipboard.
5. On Qase, navigate to the <a href="https://app.qase.io/apps" rel="nofollow noopener noreferrer" target="_blank">Apps</a> section, find the GitLab app and click <code>Install now</code>.
 The GitLab app card on the Qase Apps page, with its Install now button
 ​

Here, provide the Access token from the previous step, and URL of your GitLab instance (the field is pre-populated with the default value)

The GitLab installation form in Qase, with the access token and GitLab URL fields

Click the <code>Install</code> button. After a few seconds, you will be redirected to the <code>Apps</code> page with a confirmation message as shown below.

The Apps page confirming that the GitLab app has been installed

1. Click the <code>Install</code> button. After a few seconds, you will be redirected to the <code>Apps</code> page with a confirmation message as shown below.
 The Apps page confirming that the GitLab app has been installed
 ​

Please note, a Maintainer role is required if you choose to use a Group token.

In your repository, click any test case to open its preview and switch to the Properties tab.

Scroll down to the “Link with Apps” section, and choose the GitLab app. Then, proceed to search and link your issues.

Linked issues can be removed with the ( x ) icon.

Linking a GitLab issue from Link with Apps on the Properties tab of a test case

Test runs can be linked to a GitLab issue, from the Run Dashboard.

Under the “External Issues” section, click 'Select an Integration' to proceed. Only one GitLab issue can be linked to the Test run.

Linking a GitLab issue to a test run from External Issues on the run dashboard

Defects can be linked to a GitLab issue, from the Defect Dashboard.

Under the “External Issues” section, select the GitLab app to proceed.

Linking a GitLab issue to a defect from External Issues on the defect dashboard

Create a GitLab issue from a Qase Test Run

When you assign a negative result to a case during a test run, you will have the option to create or attach a Qase defect.

Additionally, you can select the ‘GitLab’ app from the “Choose Integration” dropdown to either create a new GitLab issue, or link an existing one.

The created or linked issue will be visible in both the defects tab of the test run and the defect section of the project.

Creating a new GitLab issue from a negative result during a test run

You can view the link to the GitLab issue in

- Defects tag of the test run
  The link to the GitLab issue shown in the defects tab of the test run
  ​
- From the Qase defect screen
  The link to the GitLab issue shown on the Qase defect screen
  ​

- You can view the link to the GitLab issue in
  - Defects tag of the test run
    The link to the GitLab issue shown in the defects tab of the test run
    ​
  - From the Qase defect screen
    The link to the GitLab issue shown on the Qase defect screen
    ​

Please note, that you will need to configure a <a href="https://help.qase.io/en/collections/3680684-qase-api-api-reporters" rel="nofollow noopener noreferrer" target="_blank">Qase API reporter</a> in your project for the results of your automated tests to be published to the Qase Test run.

Create the <code>Automated Test Run</code>:

Select the <code>Gitlab</code> option in the <code>CI/CD System</code> field:

The CI/CD System field of the run form set to Gitlab

Fill in all necessary fields and click the <code>Start a run</code> button:

The filled-in automated run form, with the Start a run button

1. Create the <code>Automated Test Run</code>:
 Creating an automated test run in Qase
 ​
2. Select the <code>Gitlab</code> option in the <code>CI/CD System</code> field:
 The CI/CD System field of the run form set to Gitlab
 ​
3. Fill in all necessary fields and click the <code>Start a run</code> button:
 The filled-in automated run form, with the Start a run button
 ​

GitLab

Create a custom design with text, images, and links

Video Tutorials

API Reference

Qase's GitHub Repo

No tickets or conversations found

Try selecting a different creation date range.

Tickets and conversations you've started through the messenger will appear here.

No tickets or conversations created by you

Try using different keywords or checking for typos.

Try selecting a different update date range.

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

No conversations found

AI title

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Conversations and tickets in {topic}

Conversations and tickets in {topic} // {subtopic}

Volume, creators and topics for your company.

Insights

Top creators

AI topics

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

GitLab

Installation

Usage

Linking your Qase Test cases

Linking your Qase Test runs

Linking your Qase Defects

Create a GitLab issue from a Qase Test Run

CI/CD Workflows