root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
gitlab-ce/doc/integration/jira/development_panel.md

6.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

Jira development panel (FREE)

Moved from GitLab Premium to GitLab Free in 13.4.

You can view GitLab activity from the Jira development panel.

When you are in GitLab, you refer to a Jira issue by ID. Then the activity for that issue is displayed in the Jira development panel.

In the Jira development panel, you can create a GitLab merge request from a branch. You can also create a GitLab branch from a Jira Cloud issue (introduced in GitLab 14.2).

Connected projects in GitLab

The Jira development panel connects to the Jira instance all GitLab projects in:

  • A top-level group, including all projects in its subgroups.
  • A personal namespace.

Where the Jira ID displayed

The information displayed in the Jira development panel depends on where you mention the Jira issue ID in GitLab.

GitLab: where you mention the Jira issue ID Jira development panel: what information is displayed
Merge request title or description Link to the merge request
Branch name Link to the branch
Commit message Link to the commit
Jira Smart Commit Custom comment, logged time, or workflow transition

Jira Smart Commits

Jira Smart Commits are special commands to process a Jira issue. With these commands, you can use GitLab to:

  • Add a custom comment to a Jira issue.
  • Log time against a Jira issue.
  • Transition a Jira issue to any status defined in the project workflow.

For more information, see Using Smart Commits in the Atlassian documentation.

Configure the integration

For an overview of how to configure the Jira development panel integration, see Agile Management - GitLab Jira development panel integration.

To simplify administration, we recommend that a GitLab group maintainer or group owner (or, if possible, instance administrator in the case of self-managed GitLab) set up the integration.

Jira usage GitLab.com customers need GitLab self-managed customers need
Atlassian cloud The GitLab for Jira Cloud app from the Atlassian Marketplace. This method offers real-time sync between GitLab.com and Jira. The method requires inbound connections for the setup and then pushes data to Jira through outbound connections. For more information, see GitLab for Jira Cloud app. The GitLab for Jira Cloud app installed manually. By default, you can install the app from the Atlassian Marketplace. The method requires inbound connections for the setup and then pushes data to Jira through outbound connections. For more information, see Connect the GitLab for Jira Cloud app for self-managed instances.
Your own server The Jira DVCS connector. This method syncs data every hour and works only with inbound connections. The method tries to set up webhooks in GitLab to implement real-time data sync, which does not work without outbound connections. The Jira DVCS connector. This method syncs data every hour and works only with inbound connections. The method tries to set up webhooks in GitLab to implement real-time data sync, which does not work without outbound connections.

Each GitLab project can be configured to connect to an entire Jira instance. That means after configuration, one GitLab project can interact with all Jira projects in that instance. For:

  • The view Jira issues feature, you must associate a GitLab project with a specific Jira project.
  • Other features, you do not have to explicitly associate a GitLab project with any single Jira project.

If you have a single Jira instance, you can pre-fill the settings. For more information, read the documentation for central administration of project integrations.

Limitations

Troubleshoot the development panel

If you use Jira on your own server, go to the Atlassian documentation for general troubleshooting information.

Cookies for Oracle's Access Manager

To support Oracle's Access Manager, GitLab sends additional cookies to enable Basic Auth. The cookie being added to each request is OBBasicAuth with a value of fromDialog.