Skip to content
Snippets Groups Projects
Commit 2f1e4740 authored by Tristan Williams's avatar Tristan Williams Committed by Evan Read
Browse files

Refresh screenshots

Current screenshots are from an older version of Jira and GitLab.
parent c03f23c4
No related branches found
No related tags found
No related merge requests found
doc/user/project/integrations/img/jira_api_token.png

60 KiB | W: 744px | H: 592px

doc/user/project/integrations/img/jira_api_token.png

20.8 KiB | W: 411px | H: 260px

doc/user/project/integrations/img/jira_api_token.png
doc/user/project/integrations/img/jira_api_token.png
doc/user/project/integrations/img/jira_api_token.png
doc/user/project/integrations/img/jira_api_token.png
  • 2-up
  • Swipe
  • Onion skin
doc/user/project/integrations/img/jira_api_token_menu.png

24.5 KiB | W: 1088px | H: 477px

doc/user/project/integrations/img/jira_api_token_menu.png

40.9 KiB | W: 725px | H: 310px

doc/user/project/integrations/img/jira_api_token_menu.png
doc/user/project/integrations/img/jira_api_token_menu.png
doc/user/project/integrations/img/jira_api_token_menu.png
doc/user/project/integrations/img/jira_api_token_menu.png
  • 2-up
  • Swipe
  • Onion skin
doc/user/project/integrations/img/jira_issue_reference.png

18 KiB | W: 856px | H: 417px

doc/user/project/integrations/img/jira_issue_reference.png

62.6 KiB | W: 764px | H: 467px

doc/user/project/integrations/img/jira_issue_reference.png
doc/user/project/integrations/img/jira_issue_reference.png
doc/user/project/integrations/img/jira_issue_reference.png
doc/user/project/integrations/img/jira_issue_reference.png
  • 2-up
  • Swipe
  • Onion skin
doc/user/project/integrations/img/jira_merge_request_close.png

20.7 KiB | W: 1388px | H: 498px

doc/user/project/integrations/img/jira_merge_request_close.png

62.8 KiB | W: 959px | H: 537px

doc/user/project/integrations/img/jira_merge_request_close.png
doc/user/project/integrations/img/jira_merge_request_close.png
doc/user/project/integrations/img/jira_merge_request_close.png
doc/user/project/integrations/img/jira_merge_request_close.png
  • 2-up
  • Swipe
  • Onion skin
doc/user/project/integrations/img/jira_service_close_comment.png

11.6 KiB

doc/user/project/integrations/img/jira_service_close_issue.png

29.9 KiB | W: 797px | H: 763px

doc/user/project/integrations/img/jira_service_close_issue.png

28.9 KiB | W: 761px | H: 831px

doc/user/project/integrations/img/jira_service_close_issue.png
doc/user/project/integrations/img/jira_service_close_issue.png
doc/user/project/integrations/img/jira_service_close_issue.png
doc/user/project/integrations/img/jira_service_close_issue.png
  • 2-up
  • Swipe
  • Onion skin
doc/user/project/integrations/img/jira_service_page.png

29.7 KiB | W: 1654px | H: 780px

doc/user/project/integrations/img/jira_service_page.png

69.1 KiB | W: 1249px | H: 663px

doc/user/project/integrations/img/jira_service_page.png
doc/user/project/integrations/img/jira_service_page.png
doc/user/project/integrations/img/jira_service_page.png
doc/user/project/integrations/img/jira_service_page.png
  • 2-up
  • Swipe
  • Onion skin
Loading
Loading
@@ -39,21 +39,17 @@ a GitLab project with any single Jira project.
If you have one Jira instance, you can pre-fill the settings page with a default
template. See the [Services Templates][services-templates] docs.
 
Configuration happens via user name and password. Connecting to a Jira Server
via CAS is not possible.
In order to enable the Jira service in GitLab, you need to first configure the
project in Jira and then enter the correct values in GitLab.
In order to enable the Jira service in GitLab, you need to first configure the project in Jira and then enter the correct values in GitLab.
 
### Configuring Jira
 
When connecting to **Jira Server**, which supports basic authentication, a **username and password** are required. Check the link below and proceed to the next step:
#### Jira Server
 
- [Setting up a user in Jira Server](jira_server_configuration.md)
When connecting to **Jira Server**, which supports basic authentication, a **username and password** are required. Note that connecting to a Jira server via CAS is not possible. [Set up a user in Jira Server](jira_server_configuration.md) first and then proceed to [Configuring GitLab](#configuring-gitlab).
 
When connecting to **Jira Cloud**, which supports authentication via API token, an **email and API token**, are required. Check the link below and proceed to the next step:
#### Jira Cloud
 
- [Setting up a user in Jira Cloud](jira_cloud_configuration.md)
When connecting to **Jira Cloud**, which supports authentication via API token, an **email and API token**, are required. [Set up a user in Jira Cloud](jira_cloud_configuration.md) first and then proceed to [Configuring GitLab](#configuring-gitlab).
 
### Configuring GitLab
 
Loading
Loading
@@ -68,7 +64,7 @@ When connecting to **Jira Cloud**, which supports authentication via API token,
> to enable Basic Auth. The cookie being added to each request is `OBBasicAuth` with
> a value of `fromDialog`.
 
To enable Jira integration in a project, navigate to the
To enable the Jira integration in a project, navigate to the
[Integrations page](project_services.md#accessing-the-project-services), click
the **Jira** service, and fill in the required details on the page as described
in the table below.
Loading
Loading
@@ -127,6 +123,12 @@ ENTITY_TITLE
 
![example of mentioning or closing the Jira issue](img/jira_issue_reference.png)
 
For example, the following commit will reference the Jira issue with `PROJECT-1` as its ID:
```bash
git commit -m "PROJECT-1 Fix spelling and grammar"
```
### Closing Jira Issues
 
Jira issues can be closed directly from GitLab by using trigger words in
Loading
Loading
@@ -142,7 +144,7 @@ the same goal:
- `Closes PROJECT-1`
- `Fixes PROJECT-1`
 
where `PROJECT-1` is the issue ID of the Jira project.
where `PROJECT-1` is the ID of the Jira issue.
 
> **Notes:**
>
Loading
Loading
@@ -174,8 +176,6 @@ with a link to the commit that resolved the issue.
 
![The GitLab integration closes Jira issue](img/jira_service_close_issue.png)
 
![The GitLab integration creates a comment and a link on Jira issue.](img/jira_service_close_comment.png)
## Troubleshooting
 
If these features do not work as expected, it is likely due to a problem with the way the integration settings were configured.
Loading
Loading
Loading
Loading
@@ -3,16 +3,18 @@
An API token is needed when integrating with Jira Cloud, follow the steps
below to create one:
 
1. Log in to <https://id.atlassian.com> with your email.
1. **Click API tokens**, then **Create API token**.
1. Log in to <https://id.atlassian.com/manage/api-tokens> with your email address.
NOTE: **Note**
It is important that the user associated with this email address has *write* access
to projects in Jira.
2. Click **Create API token**.
 
![Jira API token](img/jira_api_token_menu.png)
 
![Jira API token](img/jira_api_token.png)
 
1. Make sure to write down your new API token as you will need it in the next [steps](jira.md#configuring-gitlab).
NOTE: **Note**
It is important that the user associated with this email has 'write' access to projects in Jira.
1. Click **Copy to clipboard**, or click **View** and write down the new API token. It is required when [configuring GitLab](jira.md#configuring-gitlab).
 
The Jira configuration is complete. You are going to need this newly created token and the email you used to log in, when [configuring GitLab in the next section](jira.md#configuring-gitlab).
The Jira configuration is complete. You need the newly created token, and the associated email address, when [configuring GitLab](jira.md#configuring-gitlab) in the next section.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment