Create or update the Jira integration
Creates or updates the Jira integration.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Request Body required
Section titled “ Request Body required ”object
The URL to the Jira project which is being linked to this GitLab project (for example, https://jira.example.com).
The base URL to the Jira instance API. Web URL value is used if not set (for example, https://jira-api.example.com).
The authentication method to use with Jira. Use 0 for basic authentication, 1 for Jira personal access token, and 2 for Jira Cloud service accounts. Defaults to 0.
The email or username to use with Jira. Use an email for Jira Cloud, and a username for Jira Data Center and Jira Server. Required when using basic authentication (jira_auth_type is 0).
The Jira API token, password, or personal access token to use with Jira. When using Basic Authentication (jira_auth_type is 0), use an API token for Jira Cloud, and a password for Jira Data Center or Jira Server. For a Jira personal access token (jira_auth_type is 1), use the personal access token.
Regular expression to match Jira issue keys.
Prefix to match Jira issue keys.
The ID of one or more transitions for custom issue transitions.Ignored when jira_issue_transition_automatic is enabled. Defaults to a blank string,which disables custom transitions.
Enable viewing Jira issues in GitLab.
Keys of Jira projects to display. When issues_enabled is true, this setting filters which Jira projects are shown in GitLab. It does not restrict the API token’s access.
Turn on Jira issue creation for GitLab vulnerabilities.
Jira issue type to use when creating issues from vulnerabilities.
Key of the project to use when creating issues from vulnerabilities.This parameter is required if using the integration to create Jira issues from vulnerabilities.
When set to true, opens a prefilled form on the Jira instancewhen creating a Jira issue from a vulnerability.
Verify Jira issues referenced in commit messages exist before allowing the push.
Verify the Jira issues referenced in commit messages exist in Jira.
Verify the committer is the assignee of the Jira issues referenced in commit messages.
Verify the status of Jira issues referenced in commit messages.
Comma-separated list of allowed Jira issue statuses.
Enable comments inside Jira issues on each GitLab event (commit / merge request)
Trigger event when a commit is created or updated.
Trigger event when a merge request is created, updated, or merged.
Indicates whether to inherit the default settings. Defaults to false.
Example generated
{ "url": "example", "api_url": "example", "jira_auth_type": 1, "username": "example", "password": "example", "jira_issue_regex": "example", "jira_issue_prefix": "example", "jira_issue_transition_id": "example", "issues_enabled": "example", "project_keys": [ "example" ], "vulnerabilities_enabled": true, "vulnerabilities_issuetype": "example", "project_key": "example", "customize_jira_issue_enabled": true, "jira_check_enabled": true, "jira_exists_check_enabled": true, "jira_assignee_check_enabled": true, "jira_status_check_enabled": true, "jira_allowed_statuses_as_string": "example", "comment_on_event_enabled": true, "commit_events": true, "merge_requests_events": true, "use_inherited_settings": true}Responses
Section titled “ Responses ”OK
object
Example
{ "id": 75, "title": "Jenkins CI", "slug": "jenkins", "created_at": "2019-11-20T11:20:25.297Z", "updated_at": "2019-11-20T12:24:37.498Z"}Bad request
Unauthorized
Not found
Unprocessable entity