I'm trying to integrate JIRA issue tracker with Gitlab and following instructions from official docs.
My `/etc/gitlab/gitlab.rb' configuration file looks like
gitlab_rails['issues_tracker_jira'] = true
gitlab_rails['issues_tracker_jira_title'] = "Atlassian Jira"
gitlab_rails['issues_tracker_jira_project_url'] =
"http://localhost:7777/issues/?jql=project=:issues_tracker_id"
gitlab_rails['issues_tracker_jira_issues_url'] =
"http://localhost:7777/browse/:id"
gitlab_rails['issues_tracker_jira_new_issue_url'] =
"http://localhost:7777/secure/CreateIssue.jspa"
JIRA web app installed and running at localhost:7777
Modifying gitlab.rb file as showed above enabled JIRA in Setting tab as expected but services tab doesn't contain JIRA. Of course, I choose Atlassian Jira in Features, specified jira project name (same as gitlab project name) saved changes and in Project services tab saw Assembla, Atlassian Bamboo and others but didn't see JIRA. What I'm doing wrong?
UPDATE
As VonC pointed out, CE doesn't support JIRA fully. But, according to CE and EE comparison, CE still supports JIRA partially, in particular, mention JIRA ticket from Gitlab. As I understand, I still able to point issues to my JIRA instance and add issues in JIRA but I have to manually create project in JIRA and gitlab project name must be the same with the JIRA project name, am I right? I think so, because when I do it everything works the ony problem is log-in-problem described below.
Also, linking to JIRA doesn't work until I'm not logged in to JIRA. Is there any way to provide JIRA credentials to Gitlab CE?
We are using gitlab-ce 8.2.2-ce.0 and JIRA 6.4.11. I didn't have to configure anything in gitlab.rb.
First, configure the template so you don't have to do everything for each new project:
http://localhost:7777/admin/application_settings/services
Open "JIRA" and exactly set this (including the ##-stuff - don't replace it):
Project url: http://localhost:7777/browse/#project-name#
Issues url: http://localhost:7777/browse/:id
New issue url: http://localhost:7777/secure/CreateIssue!default.jspa?selectedProjectId=#project-id#
Then for each project, go to "Project > Settings > Services", activate JIRA and adapt the settings to use the correct project name and ID.
gitlab project name must be the same with the JIRA project name, am I right?
No, this is not necessary.
Related
I try to connect my Kiwi TCMS to JIRA server, but when i try to report a bug to jira it open always same project. How to define link betwen projects in Kiwi TCMS and JIRA server? Where can i configure that parameters?
I only add jira to bugtracker in kiwi tcms like described in docs. I add link to jira, and username\password for my account in jira. Dont see any other options in kiwi tcms interface.
By what I was able to gather when reading the documentation to set up my Jira integration was that all the "integration" does is provide an autofill link to recreate the ticket in Jira (one way, KiwiTCMS -> Jira).
I would suggest trying to change the api link to one that points at project rather than the organization.atlassian.net link. Otherwise, it doesn't appear to be possible at this time :(
By default, kiwi searches project in jira matched with product name of your test plan. If there is no matches , it opened the first project available for your user.
https://kiwitcms.readthedocs.io/en/latest/_modules/tcms/issuetracker/types.html#JIRA.get_project_from_jira
There are three options (kiwi version 11.7):
in the kiwi, rename product name to match with the name of project in jira (https://jira.readthedocs.io/api.html#jira.client.JIRA.projects);
create a jira user with only one project available to search and used it for kiwi;
customize get_project_from_jira function, so it returns the desired project (https://kiwitcms.readthedocs.io/en/latest/installing_docker.html#customization)
I would like to exploit the integration between the two tools to be able to automatically create a branch in GitLab for every new Bug or Feature ticket created in Jira.
I would like to know if (i) it is possible; (ii) what is the link between the two tools (I guess the unique ID number assigned by Jira); (iii) assuming the first point is true, what happens to the created branch when I close the Jira issue (e.g. I've mistakenly created a bug fix that was not needed).
I've used Jira in conjunction with GitHub so I'll try my best to help you.
I) This is definitely possible.
II) We used to use the unique ID given to a ticket and include it within in the branch name this creates a link between both tools. Any changes committed on the branch will be shown in JIRA.
III) From experience when this happens the branch will persist and will need to be deleted manually using a console we used to use a .git console and used a delete command.
I also found through a quick google search some documentation on GitLab on integration with JIRA as well as some insight on creating branches.
Doc - https://docs.gitlab.com/ee/user/project/integrations/jira.html
Branch - https://gitlab.com/gitlab-org/gitlab-ce/issues/3886
Hope this helps.
im trying to setup some projects in jira, we have existing bitbucket repos. Our jira projects have issues we have put in, is it possible to view these jira issues in bitbucket
You can link JIRA to BitBucket by following this tutorial: Linking Bitbucket and GitHub accounts to JIRA. This uses the JIRA DVCS Connector add-on which I believe is a free download from the Atlassian Marketplace.
Branches, pull requests and commit messages can reference JIRA issues. I'm not sure whether you can link existing branches etc though unless they reference the issue in JIRA directly.
We have self hosted GitLab CE and Jira, we want
link git commit with jira issue
link git commit with jira issue status, like we can start/move/close issue by git issues
limit above operations on specific branches, e.g., change issue status only when commits on master branch since we perform merge request for every single feature/bug
but only GitLab EE built-in supports Jira integration, how could I do that for GitLab CE?
I'm on GitLab CE 7.8.2, Jira+Agile 6.4
I think there is now a better way:
https://docs.gitlab.com/ce/user/project/integrations/jira.html
GitLab can be configured to interact with JIRA. Configuration happens via user name and password. Connecting to a JIRA server via CAS is not possible.
Each project can be configured to connect to a different JIRA instance, see the configuration section. If you have one JIRA instance you can pre-fill the settings page with a default template. To configure the template see the Services Templates document.
Once the project is connected to JIRA, you can reference and close the issues in JIRA directly from GitLab.
You can take a look at this project : https://github.com/akraxx/gitlab-jira-integration. It's a Java application, so you will need a server with a JVM to run it.
Follow the README to know how to configure it :)
Note that, with GitLab 13.3 (August 2020), you don't have to setup a third-party integration on each project anymore.
You can do so at your managed Gitlab instance level (free edition).
Instance-level project integration management for external services
Administrators of self-managed GitLab can now integrate third-party services with all projects on the instance from a single interface.
Previously, integrations had to be configured per project, which meant that if an instance had thousands of projects, thousands of individual configurations had to be manually configured. Not only was this time-consuming, but it was also error-prone, hard to update, and made it difficult to enforce integrations as a policy.
By configuring integrations across all projects, administrators save themselves and their project owners incredible amounts of time and effort.
This is the first iteration of this functionality. In upcoming releases, we will expand this feature to the group level, add more configuration and compliance options, and more.
See Documentation and Issue.
Plus, with GitLab 13.4 (September 2020)
GitLab for Jira and DVCS Connector now in Core
For users of Jira GitLab, the GitLab for Jira app and the DVCS Connector
allow you to display information about GitLab
commits and merge requests directly in Jira.
Combined with our native
integration with Jira, you can easily move back and forth between the
two applications as you work.
These features were previously available only in our Premium plan, but
are now available to all users!
See Documentation and Issue.
See GitLab 13.6 (November 2020)
Group-level management of project integrations
In GitLab 13.3, we added the ability to enable an integration across an entire instance.
With GitLab 13.6, that feature is being expanded to allow integrations to be managed at the group level as well!
Group owners can now add an integration to a group, and that integration will be inherited by all projects under that group.
This has the potential for saving massive amounts of time, as many organizations have specific integrations that they want rolled out to every project they create.
A great example of this is using our Jira integration. If you’re using Jira, it’s almost always across the whole company. Some of these companies have thousands of projects and therefore had to configure each and every one of those integrations individually.
With group-level management of project integrations, you can add the integration at each parent group, reducing the amount of configuration required by orders of magnitude!
Read more in our announcement on the GitLab blog.
See Documentation and Epic.
With GitLab 13.10 (March 2021):
View Jira issue details in GitLab
Users of our Jira issue list feature can now view the details of an issue directly inside of GitLab! This MVC enables developers to see the details, labels, and comments on an issue, giving them the ability to stay in GitLab while working on Jira issues.
Our goal is to empower developers to stay inside of GitLab during the majority of their day, and this is now one less trip to Jira you’ll have to make.
In GitLab 13.10, this feature is available if you enable a feature flag. This feature will be enabled by default in GitLab 13.11.
See Documentation and Epic.
At the moment I think the GitLab Listener add-on for JIRA is the only way to integrate GitLab CE and JIRA. You can use commit messages to generate JIRA worklogs, comments and activities, as well as execute workflow transitions. The add-on also tries to map GitLab users to JIRA users in order to link worklogs, comments, etc. to the right user.
It's a simple add-on and maybe it does not cover all your requirements, but it's better than nothing :).
I have installed Jira and the subversion plugin (with success from what i can tell from the administration panel - subv. plugin installed).
I then add a repository that I have created on the file system, BUT i cannot see an option which will link/connect a new or existing project to a SVN repository. What i want to do is link a project with a repository so I can track commits made to the project (link commits with issues). After some searching i found that this is possible but I cannot figure a way to do it.
Do I need another plugin for that? I have tried googling for the last hours but I cannot find anything related.
regards,
The way SVN-Jira linking works by default is to simply put the issue identifier of the Jira issue in the comment when committing to the SVN repository.
It can be helpful to enable comment editing in the repository, if you have past commits or users who forget to add comments when committing.
Example commit comment:
Fixed problem with login. See issue MYJIRAPROJECT-26 in issue tracker.
There's a service in Jira which scans the SVN repository at regular intervals, and builds a cache of any SVN revisions where an issue identifier appears. Depending on the polling interval, it make take a few minutes for the commit to show up in Jira.
The polling time is controlled by the JIRA Service for the SVN plugin. See Admin, Services.
~Matt
you can enforce that future subversion commits require a jira issue reference for more reliable--than relying on your programmer's word ;)--jira-subversion integration
the jira commit acceptance plugin can be configured to block commits that don't include a valid (defined by subversion-jira project mapping and/or regular expression as appropriate to your situation) jira issue reference in the commit comment
reliable jira-subversion linkage availability allows handy stuff like:
Integration with issue trackers