- Make sure to replace the `Redirect URI` HOST by your's (or `gitlab` in case you're using GitLab.com)
- Make sure the logged-in user on GitLab has access to the projects you want to import to Jira.
- Only the `api` scope needs to be checked
2. Save the generated 'Application id' and 'Secret', you'll need this information when configuring Jira.
- Check `api` in the Scopes section.
2. Click `Save application`. You will see the generated 'Application Id' and 'Secret' values.
Copy these values that you will use on the JIRA configuration side.
## On Jira
## JIRA Configuration
1. Go to `Application -> DVCS accounts` and click on `Link GitHub account`
1. In JIRA, from the gear menu at the top right, go to `Applications`. Navigate to `DVCS accounts`
from the left navigation menu. Click `Link GitHub account` to start creating a new integration.
(We are pretending to be GitHub in this integration until there is further platform support from JIRA.)
2. Provide the required information
2. Complete the form
Select GitHub Enterprise for the `Host` field.
For the `Team or User Account` field, enter the group name of a GitLab group that you have access to.
- Make sure to replace the `Host URL` HOST by your's (keeping the rest of the URL `/-/jira` unchanged)
- Paste the `Application id` provided by GitLab on `Client ID`
- Paste the `Secret` provided by GitLab on `Client Secret`
For the `Host URL` field, enter `https://<your-gitlab-instance-domain>/-/jira`,
replacing `<your-gitlab-instance-domain>` appropriately. So for example, if you are using GitLab.com,
this would be `https://gitlab.com/-/jira`.
>**Note:**
In case you have multiple groups with projects that you want to import, you'll follow this process for each one of these groups.
So let's say your username on GitLab is 'mytest', but you have another group called 'group-a'. In order to import
your projects ('mytest') and all projects within 'group-a', you'll create one integration providing 'mytest' as 'Team or User Account' and another one providing 'group-a'.
For the `Client ID` field, use the `Application ID` value from the previous section.
3. Click `Add` and finish the authorization process
For the `Client Secret` field, use the `Secret` value from the previous section.
At that point you're done! All Projects Branches and Commits (within the configured groups) referring your Jira issues will be automatically
imported.
The import process can take a few seconds (or minutes) depending on how many projects and commits you have on GitLab.
Ensure that the rest of the checkboxes are checked.
3. Click `Add` to complete and create the integration.
JIRA takes up to a few minutes to know about (import behind the scenes) all the commits and branches
for all the projects in the GitLab group you specified in the previous step. These are refreshed
every 60 minutes.
>**Note:**
Jira automatically fetches your GitLab instance looking for new projects and referenced branches and projects in a 60 minute interval.
In the future, we plan on implementating real-time integration.
4. Repeat the above steps for each GitLab group's projects that you want to be made known to JIRA.
Specify the GitLab group name accordingly. (Note that you can also specify GitLab user names, as they
are really GitLab "groups" behind the scenes. In that case, all the projects for that user would
be made known to JIRA, up to the permissions of the user setting up the integration.)
You can now see the linked `branches` and `commits` when entering a Jira issue.
You can now see the linked `branches` and `commits` when entering a JIRA issue.
...
...
@@ -65,6 +86,5 @@ Click these links for more information.
