realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/integration/jira/configure.md
Vinay Keshava 081c1a8e73 New upstream version 15.9.2+ds1
2023-04-23 21:23:45 +05:30

4.1 KiB
Raw Blame History

stage group info
Manage Integrations To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments

Configure the Jira integration (FREE)

You can set up the Jira integration by configuring your project settings in GitLab. You can also configure these settings at a group level, and for self-managed GitLab, at an instance level.

Prerequisites:

  • Ensure your GitLab installation does not use a relative URL.
  • For Jira Server, ensure you have a Jira username and password. See authentication in Jira.
  • For Jira on Atlassian cloud, ensure you have an API token and the email address you used to create the token. See authentication in Jira.

To configure your project:

  1. On the top bar, select Main menu > Projects and find your project.

  2. On the left sidebar, select Settings > Integrations.

  3. Select Jira.

  4. Select Enable integration.

  5. Select Trigger actions. Your choice determines whether a mention of Jira issue (in a GitLab commit, merge request, or both) creates a cross-link in Jira back to GitLab.

  6. To comment in the Jira issue when a Trigger action is made in GitLab, select Enable comments.

  7. To transition Jira issues when a closing reference is made in GitLab, select Enable Jira transitions.

  8. Provide Jira configuration information:

    • Web URL: The base URL to the Jira instance web interface you're linking to this GitLab project, such as https://jira.example.com.
    • Jira API URL: The base URL to the Jira instance API, such as https://jira-api.example.com. Defaults to the Web URL value if not set. Leave blank if using Jira on Atlassian cloud.
    • Username or Email: For Jira Server, use username. For Jira on Atlassian cloud, use email.
    • Password/API token: Use password for Jira Server or API token for Jira on Atlassian cloud.

  9. To enable users to view Jira issues inside the GitLab project, select Enable Jira issues and enter a Jira project key.

    You can display issues only from a single Jira project in a given GitLab project.

    WARNING: If you enable Jira issues with this setting, all users with access to this GitLab project can view all issues from the specified Jira project.

  10. To enable issue creation for vulnerabilities, select Enable Jira issue creation from vulnerabilities.

  11. Select the Jira issue type. If the dropdown list is empty, select refresh ({retry}) and try again.

  12. To verify the Jira connection is working, select Test settings.

  13. Select Save changes.

Your GitLab project can now interact with all Jira projects in your instance and the project now displays a Jira link that opens the Jira project.

Migrate from Jira Server to Jira Cloud in GitLab

To migrate from Jira Server to Jira Cloud in GitLab and maintain your Jira integration:

  1. On the top bar, select Main menu > Projects and find your project.
  2. On the left sidebar, select Settings > Integrations.
  3. Select Jira.
  4. In Web URL, enter the new Jira site URL (for example, https://myjirasite.atlassian.net).
  5. In Username or Email, enter the username or email registered on your Jira profile.
  6. Create an API token, and copy that value.
  7. In Password or API token, paste the API token value.
  8. Optional. Select Test settings to check if the connection is working.
  9. Select Save changes.