published on Wednesday, Aug 26, 2026 by Pulumi
published on Wednesday, Aug 26, 2026 by Pulumi
The gitlab.GroupIntegrationJira resource manages the lifecycle of a group integration with Jira.
Upstream API: GitLab REST API docs
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as gitlab from "@pulumi/gitlab";
const example = new gitlab.Group("example", {
name: "example-group",
path: "example-group",
description: "An example group",
});
const jira = new gitlab.GroupIntegrationJira("jira", {
group: example.id,
url: "https://jira.example.com",
username: "user",
password: "mypass",
});
import pulumi
import pulumi_gitlab as gitlab
example = gitlab.Group("example",
name="example-group",
path="example-group",
description="An example group")
jira = gitlab.GroupIntegrationJira("jira",
group=example.id,
url="https://jira.example.com",
username="user",
password="mypass")
package main
import (
"github.com/pulumi/pulumi-gitlab/sdk/v10/go/gitlab"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
example, err := gitlab.NewGroup(ctx, "example", &gitlab.GroupArgs{
Name: pulumi.String("example-group"),
Path: pulumi.String("example-group"),
Description: pulumi.String("An example group"),
})
if err != nil {
return err
}
_, err = gitlab.NewGroupIntegrationJira(ctx, "jira", &gitlab.GroupIntegrationJiraArgs{
Group: example.ID().ToIDOutput().ToStringOutput(),
Url: pulumi.String("https://jira.example.com"),
Username: pulumi.String("user"),
Password: pulumi.String("mypass"),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using GitLab = Pulumi.GitLab;
return await Deployment.RunAsync(() =>
{
var example = new GitLab.Group("example", new()
{
Name = "example-group",
Path = "example-group",
Description = "An example group",
});
var jira = new GitLab.GroupIntegrationJira("jira", new()
{
Group = example.Id,
Url = "https://jira.example.com",
Username = "user",
Password = "mypass",
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gitlab.Group;
import com.pulumi.gitlab.GroupArgs;
import com.pulumi.gitlab.GroupIntegrationJira;
import com.pulumi.gitlab.GroupIntegrationJiraArgs;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var example = new Group("example", GroupArgs.builder()
.name("example-group")
.path("example-group")
.description("An example group")
.build());
var jira = new GroupIntegrationJira("jira", GroupIntegrationJiraArgs.builder()
.group(example.id())
.url("https://jira.example.com")
.username("user")
.password("mypass")
.build());
}
}
resources:
example:
type: gitlab:Group
properties:
name: example-group
path: example-group
description: An example group
jira:
type: gitlab:GroupIntegrationJira
properties:
group: ${example.id}
url: https://jira.example.com
username: user
password: mypass
pulumi {
required_providers {
gitlab = {
source = "pulumi/gitlab"
}
}
}
resource "gitlab_group" "example" {
name = "example-group"
path = "example-group"
description = "An example group"
}
resource "gitlab_groupintegrationjira" "jira" {
group = gitlab_group.example.id
url = "https://jira.example.com"
username = "user"
password = "mypass"
}
Create GroupIntegrationJira Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new GroupIntegrationJira(name: string, args: GroupIntegrationJiraArgs, opts?: CustomResourceOptions);@overload
def GroupIntegrationJira(resource_name: str,
args: GroupIntegrationJiraArgs,
opts: Optional[ResourceOptions] = None)
@overload
def GroupIntegrationJira(resource_name: str,
opts: Optional[ResourceOptions] = None,
group: Optional[str] = None,
url: Optional[str] = None,
password: Optional[str] = None,
jira_issue_transition_automatic: Optional[bool] = None,
issues_enabled: Optional[bool] = None,
jira_auth_type: Optional[int] = None,
jira_issue_prefix: Optional[str] = None,
jira_issue_regex: Optional[str] = None,
api_url: Optional[str] = None,
jira_issue_transition_id: Optional[str] = None,
merge_requests_events: Optional[bool] = None,
commit_events: Optional[bool] = None,
project_keys: Optional[Sequence[str]] = None,
comment_on_event_enabled: Optional[bool] = None,
use_inherited_settings: Optional[bool] = None,
username: Optional[str] = None)func NewGroupIntegrationJira(ctx *Context, name string, args GroupIntegrationJiraArgs, opts ...ResourceOption) (*GroupIntegrationJira, error)public GroupIntegrationJira(string name, GroupIntegrationJiraArgs args, CustomResourceOptions? opts = null)
public GroupIntegrationJira(String name, GroupIntegrationJiraArgs args)
public GroupIntegrationJira(String name, GroupIntegrationJiraArgs args, CustomResourceOptions options)
type: gitlab:GroupIntegrationJira
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
resource "gitlab_group_integration_jira" "name" {
# resource properties
}Parameters
- name string
- The unique name of the resource.
- args GroupIntegrationJiraArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args GroupIntegrationJiraArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args GroupIntegrationJiraArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args GroupIntegrationJiraArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args GroupIntegrationJiraArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var groupIntegrationJiraResource = new GitLab.GroupIntegrationJira("groupIntegrationJiraResource", new()
{
Group = "string",
Url = "string",
Password = "string",
JiraIssueTransitionAutomatic = false,
IssuesEnabled = false,
JiraAuthType = 0,
JiraIssuePrefix = "string",
JiraIssueRegex = "string",
ApiUrl = "string",
JiraIssueTransitionId = "string",
MergeRequestsEvents = false,
CommitEvents = false,
ProjectKeys = new[]
{
"string",
},
CommentOnEventEnabled = false,
UseInheritedSettings = false,
Username = "string",
});
example, err := gitlab.NewGroupIntegrationJira(ctx, "groupIntegrationJiraResource", &gitlab.GroupIntegrationJiraArgs{
Group: pulumi.String("string"),
Url: pulumi.String("string"),
Password: pulumi.String("string"),
JiraIssueTransitionAutomatic: pulumi.Bool(false),
IssuesEnabled: pulumi.Bool(false),
JiraAuthType: pulumi.Int(0),
JiraIssuePrefix: pulumi.String("string"),
JiraIssueRegex: pulumi.String("string"),
ApiUrl: pulumi.String("string"),
JiraIssueTransitionId: pulumi.String("string"),
MergeRequestsEvents: pulumi.Bool(false),
CommitEvents: pulumi.Bool(false),
ProjectKeys: pulumi.StringArray{
pulumi.String("string"),
},
CommentOnEventEnabled: pulumi.Bool(false),
UseInheritedSettings: pulumi.Bool(false),
Username: pulumi.String("string"),
})
resource "gitlab_group_integration_jira" "groupIntegrationJiraResource" {
lifecycle {
create_before_destroy = true
}
group = "string"
url = "string"
password = "string"
jira_issue_transition_automatic = false
issues_enabled = false
jira_auth_type = 0
jira_issue_prefix = "string"
jira_issue_regex = "string"
api_url = "string"
jira_issue_transition_id = "string"
merge_requests_events = false
commit_events = false
project_keys = ["string"]
comment_on_event_enabled = false
use_inherited_settings = false
username = "string"
}
var groupIntegrationJiraResource = new GroupIntegrationJira("groupIntegrationJiraResource", GroupIntegrationJiraArgs.builder()
.group("string")
.url("string")
.password("string")
.jiraIssueTransitionAutomatic(false)
.issuesEnabled(false)
.jiraAuthType(0)
.jiraIssuePrefix("string")
.jiraIssueRegex("string")
.apiUrl("string")
.jiraIssueTransitionId("string")
.mergeRequestsEvents(false)
.commitEvents(false)
.projectKeys("string")
.commentOnEventEnabled(false)
.useInheritedSettings(false)
.username("string")
.build());
group_integration_jira_resource = gitlab.GroupIntegrationJira("groupIntegrationJiraResource",
group="string",
url="string",
password="string",
jira_issue_transition_automatic=False,
issues_enabled=False,
jira_auth_type=0,
jira_issue_prefix="string",
jira_issue_regex="string",
api_url="string",
jira_issue_transition_id="string",
merge_requests_events=False,
commit_events=False,
project_keys=["string"],
comment_on_event_enabled=False,
use_inherited_settings=False,
username="string")
const groupIntegrationJiraResource = new gitlab.GroupIntegrationJira("groupIntegrationJiraResource", {
group: "string",
url: "string",
password: "string",
jiraIssueTransitionAutomatic: false,
issuesEnabled: false,
jiraAuthType: 0,
jiraIssuePrefix: "string",
jiraIssueRegex: "string",
apiUrl: "string",
jiraIssueTransitionId: "string",
mergeRequestsEvents: false,
commitEvents: false,
projectKeys: ["string"],
commentOnEventEnabled: false,
useInheritedSettings: false,
username: "string",
});
type: gitlab:GroupIntegrationJira
properties:
apiUrl: string
commentOnEventEnabled: false
commitEvents: false
group: string
issuesEnabled: false
jiraAuthType: 0
jiraIssuePrefix: string
jiraIssueRegex: string
jiraIssueTransitionAutomatic: false
jiraIssueTransitionId: string
mergeRequestsEvents: false
password: string
projectKeys:
- string
url: string
useInheritedSettings: false
username: string
GroupIntegrationJira Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The GroupIntegrationJira resource accepts the following input properties:
- Group string
- ID or full path of the group you want to activate integration on.
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- Url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Project
Keys List<string> - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- Group string
- ID or full path of the group you want to activate integration on.
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- Url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Project
Keys []string - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- group string
- ID or full path of the group you want to activate integration on.
- password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- api_
url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment_
on_ boolevent_ enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit_
events bool - Enable notifications for commit events
- issues_
enabled bool - Enable viewing Jira issues in GitLab.
- jira_
auth_ numbertype - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira_
issue_ stringprefix - Prefix to match Jira issue keys.
- jira_
issue_ stringregex - Regular expression to match Jira issue keys.
- jira_
issue_ booltransition_ automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira_
issue_ stringtransition_ id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge_
requests_ boolevents - Enable notifications for merge request events
- project_
keys list(string) - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use_
inherited_ boolsettings - Indicates whether or not to inherit default settings. Defaults to false.
- username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- group String
- ID or full path of the group you want to activate integration on.
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- url String
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth IntegerType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- project
Keys List<String> - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- group string
- ID or full path of the group you want to activate integration on.
- password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment
On booleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events boolean - Enable notifications for commit events
- issues
Enabled boolean - Enable viewing Jira issues in GitLab.
- jira
Auth numberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira
Issue stringPrefix - Prefix to match Jira issue keys.
- jira
Issue stringRegex - Regular expression to match Jira issue keys.
- jira
Issue booleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge
Requests booleanEvents - Enable notifications for merge request events
- project
Keys string[] - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use
Inherited booleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- group str
- ID or full path of the group you want to activate integration on.
- password str
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- url str
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- api_
url str - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment_
on_ boolevent_ enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit_
events bool - Enable notifications for commit events
- issues_
enabled bool - Enable viewing Jira issues in GitLab.
- jira_
auth_ inttype - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira_
issue_ strprefix - Prefix to match Jira issue keys.
- jira_
issue_ strregex - Regular expression to match Jira issue keys.
- jira_
issue_ booltransition_ automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira_
issue_ strtransition_ id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge_
requests_ boolevents - Enable notifications for merge request events
- project_
keys Sequence[str] - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use_
inherited_ boolsettings - Indicates whether or not to inherit default settings. Defaults to false.
- username str
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- group String
- ID or full path of the group you want to activate integration on.
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- url String
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth NumberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- project
Keys List<String> - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
Outputs
All input properties are implicitly available as output properties. Additionally, the GroupIntegrationJira resource produces the following output properties:
- Active bool
- Whether the integration is active.
- Created
At string - The ISO8601 date/time that this integration was activated at in UTC.
- Id string
- The provider-assigned unique ID for this managed resource.
- Title string
- Title of the integration.
- Updated
At string - The ISO8601 date/time that this integration was last updated at in UTC.
- Active bool
- Whether the integration is active.
- Created
At string - The ISO8601 date/time that this integration was activated at in UTC.
- Id string
- The provider-assigned unique ID for this managed resource.
- Title string
- Title of the integration.
- Updated
At string - The ISO8601 date/time that this integration was last updated at in UTC.
- active bool
- Whether the integration is active.
- created_
at string - The ISO8601 date/time that this integration was activated at in UTC.
- id string
- The provider-assigned unique ID for this managed resource.
- title string
- Title of the integration.
- updated_
at string - The ISO8601 date/time that this integration was last updated at in UTC.
- active Boolean
- Whether the integration is active.
- created
At String - The ISO8601 date/time that this integration was activated at in UTC.
- id String
- The provider-assigned unique ID for this managed resource.
- title String
- Title of the integration.
- updated
At String - The ISO8601 date/time that this integration was last updated at in UTC.
- active boolean
- Whether the integration is active.
- created
At string - The ISO8601 date/time that this integration was activated at in UTC.
- id string
- The provider-assigned unique ID for this managed resource.
- title string
- Title of the integration.
- updated
At string - The ISO8601 date/time that this integration was last updated at in UTC.
- active bool
- Whether the integration is active.
- created_
at str - The ISO8601 date/time that this integration was activated at in UTC.
- id str
- The provider-assigned unique ID for this managed resource.
- title str
- Title of the integration.
- updated_
at str - The ISO8601 date/time that this integration was last updated at in UTC.
- active Boolean
- Whether the integration is active.
- created
At String - The ISO8601 date/time that this integration was activated at in UTC.
- id String
- The provider-assigned unique ID for this managed resource.
- title String
- Title of the integration.
- updated
At String - The ISO8601 date/time that this integration was last updated at in UTC.
Look up Existing GroupIntegrationJira Resource
Get an existing GroupIntegrationJira resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: GroupIntegrationJiraState, opts?: CustomResourceOptions): GroupIntegrationJira@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
api_url: Optional[str] = None,
comment_on_event_enabled: Optional[bool] = None,
commit_events: Optional[bool] = None,
created_at: Optional[str] = None,
group: Optional[str] = None,
issues_enabled: Optional[bool] = None,
jira_auth_type: Optional[int] = None,
jira_issue_prefix: Optional[str] = None,
jira_issue_regex: Optional[str] = None,
jira_issue_transition_automatic: Optional[bool] = None,
jira_issue_transition_id: Optional[str] = None,
merge_requests_events: Optional[bool] = None,
password: Optional[str] = None,
project_keys: Optional[Sequence[str]] = None,
title: Optional[str] = None,
updated_at: Optional[str] = None,
url: Optional[str] = None,
use_inherited_settings: Optional[bool] = None,
username: Optional[str] = None) -> GroupIntegrationJirafunc GetGroupIntegrationJira(ctx *Context, name string, id IDInput, state *GroupIntegrationJiraState, opts ...ResourceOption) (*GroupIntegrationJira, error)public static GroupIntegrationJira Get(string name, Input<string> id, GroupIntegrationJiraState? state, CustomResourceOptions? opts = null)public static GroupIntegrationJira get(String name, Output<String> id, GroupIntegrationJiraState state, CustomResourceOptions options)resources: _: type: gitlab:GroupIntegrationJira get: id: ${id}import {
to = gitlab_group_integration_jira.example
id = "${id}"
}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Active bool
- Whether the integration is active.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Created
At string - The ISO8601 date/time that this integration was activated at in UTC.
- Group string
- ID or full path of the group you want to activate integration on.
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- Project
Keys List<string> - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Title string
- Title of the integration.
- Updated
At string - The ISO8601 date/time that this integration was last updated at in UTC.
- Url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- Active bool
- Whether the integration is active.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Created
At string - The ISO8601 date/time that this integration was activated at in UTC.
- Group string
- ID or full path of the group you want to activate integration on.
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- Project
Keys []string - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Title string
- Title of the integration.
- Updated
At string - The ISO8601 date/time that this integration was last updated at in UTC.
- Url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- active bool
- Whether the integration is active.
- api_
url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment_
on_ boolevent_ enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit_
events bool - Enable notifications for commit events
- created_
at string - The ISO8601 date/time that this integration was activated at in UTC.
- group string
- ID or full path of the group you want to activate integration on.
- issues_
enabled bool - Enable viewing Jira issues in GitLab.
- jira_
auth_ numbertype - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira_
issue_ stringprefix - Prefix to match Jira issue keys.
- jira_
issue_ stringregex - Regular expression to match Jira issue keys.
- jira_
issue_ booltransition_ automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira_
issue_ stringtransition_ id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge_
requests_ boolevents - Enable notifications for merge request events
- password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- project_
keys list(string) - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title string
- Title of the integration.
- updated_
at string - The ISO8601 date/time that this integration was last updated at in UTC.
- url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- use_
inherited_ boolsettings - Indicates whether or not to inherit default settings. Defaults to false.
- username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- active Boolean
- Whether the integration is active.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- created
At String - The ISO8601 date/time that this integration was activated at in UTC.
- group String
- ID or full path of the group you want to activate integration on.
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth IntegerType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- project
Keys List<String> - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title String
- Title of the integration.
- updated
At String - The ISO8601 date/time that this integration was last updated at in UTC.
- url String
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- active boolean
- Whether the integration is active.
- api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment
On booleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events boolean - Enable notifications for commit events
- created
At string - The ISO8601 date/time that this integration was activated at in UTC.
- group string
- ID or full path of the group you want to activate integration on.
- issues
Enabled boolean - Enable viewing Jira issues in GitLab.
- jira
Auth numberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira
Issue stringPrefix - Prefix to match Jira issue keys.
- jira
Issue stringRegex - Regular expression to match Jira issue keys.
- jira
Issue booleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge
Requests booleanEvents - Enable notifications for merge request events
- password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- project
Keys string[] - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title string
- Title of the integration.
- updated
At string - The ISO8601 date/time that this integration was last updated at in UTC.
- url string
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- use
Inherited booleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- active bool
- Whether the integration is active.
- api_
url str - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment_
on_ boolevent_ enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit_
events bool - Enable notifications for commit events
- created_
at str - The ISO8601 date/time that this integration was activated at in UTC.
- group str
- ID or full path of the group you want to activate integration on.
- issues_
enabled bool - Enable viewing Jira issues in GitLab.
- jira_
auth_ inttype - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira_
issue_ strprefix - Prefix to match Jira issue keys.
- jira_
issue_ strregex - Regular expression to match Jira issue keys.
- jira_
issue_ booltransition_ automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira_
issue_ strtransition_ id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge_
requests_ boolevents - Enable notifications for merge request events
- password str
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- project_
keys Sequence[str] - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title str
- Title of the integration.
- updated_
at str - The ISO8601 date/time that this integration was last updated at in UTC.
- url str
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- use_
inherited_ boolsettings - Indicates whether or not to inherit default settings. Defaults to false.
- username str
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
- active Boolean
- Whether the integration is active.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com. Required if jiraauthtype is 2.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- created
At String - The ISO8601 date/time that this integration was activated at in UTC.
- group String
- ID or full path of the group you want to activate integration on.
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth NumberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. 2 means Jira Cloud service accounts. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false. This value cannot be imported, and will not perform drift detection if changed outside Terraform.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token. When your authentication method is a Jira Cloud Service Account, use an API token.
- project
Keys List<String> - Keys of Jira projects. When issuesEnabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title String
- Title of the integration.
- updated
At String - The ISO8601 date/time that this integration was last updated at in UTC.
- url String
- The URL to the JIRA project which is being linked to this GitLab group. For example, https://jira.example.com.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0). Should not be provided when using a Jira Cloud Service Account
Import
Starting in Terraform v1.5.0, you can use an import block to import gitlab.GroupIntegrationJira. For example:
Importing using the CLI is supported with the following syntax:
You can import a gitlab.GroupIntegrationJira state using the group ID, for example:
$ pulumi import gitlab:index/groupIntegrationJira:GroupIntegrationJira jira 12345
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- GitLab pulumi/pulumi-gitlab
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
gitlabTerraform Provider.
published on Wednesday, Aug 26, 2026 by Pulumi