The Jira connector uses the REST API v2 to create Atlassian Jira issues.
Jira on-premise deployments (Server and Data Center) are not supported.
Create connectors in Kibanaedit
You can create connectors in Stack Management > Connectors or as needed when you’re creating a rule. For example:
Jira connectors have the following configuration properties:
- The name of the connector.
- Jira instance URL.
- Project key
- Jira project key.
- The account email for HTTP Basic authentication.
- API token
- Jira API authentication token for HTTP Basic authentication.
Create preconfigured connectorsedit
If you are running Kibana on-prem, you can define connectors by
xpack.actions.preconfigured settings to your
xpack.actions.preconfigured: my-jira: name: preconfigured-jira-connector-type actionTypeId: .jira config: apiUrl: https://elastic.atlassian.net projectKey: ES secrets: email: testuser apiToken: tokenkeystorevalue
Config defines information for the connector type.
- An address that corresponds to URL.
- A key that corresponds to Project Key.
Secrets defines sensitive information for the connector type.
- A string that corresponds to Email.
- A string that corresponds to API Token. Should be stored in the Kibana keystore.
You can test connectors with the run connector API or as you’re creating or editing the connector in Kibana. For example:
Jira actions have the following configuration properties.
- Issue type
- The type of the issue.
- The priority of the incident.
- The labels for the incident.
- A title for the issue, used for searching the contents of the knowledge base.
- The details about the incident.
The ID or key of the parent issue. Only for
- Additional comments
- Additional information for the client, such as how to troubleshoot the issue.
Connector networking configurationedit
Use the Action configuration settings to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use
xpack.actions.customHostSettings to set per-host configurations.