Under construction
Plugin Jira Endpoint
Description
The Jira endpoint connection configures the necessary parameters to establish a connection with a Jira instance, including authentication and base URL setup. Also, it performs a test call to verify the correctness of the configuration. We need to indicate the Jira project with which we want to exchange tickets. Additionally, it works as an outbound connection, allowing us to put new tickets, ticket updates, new comments, and new attachments from other service desks into our Jira project.
Outbound Configuration
| Field | Supported Values | Description |
|---|---|---|
| Topics | Any string | Refers to the RabbitMQ queue topics to which our sender is subscribed. For 1Bonding instances, this parameter should indicate the subscriberId of the owner of the 1Gateway instance where it is installed, following the pattern: *.subscriberId.* . We can indicate a list of topics separated by commas. |
| Queue name | Any string | Queue name for receiving Normalized Incidents from other service desks. |
| Throttle traffic when queue fills up | true / false | This check indicates that the system will limit or reduce message traffic when the message queue reaches its maximum capacity. The idea is to prevent the queue from becoming saturated or overflowing, which could cause performance issues or message loss. |
| Durable | true / false | This check refers to the durability of messages or queues in RabbitMQ. When marked as "durable," it means that messages and/or queues will be persistent, meaning they will survive a server or messaging system restart. This is important to ensure message integrity and availability, especially in the event of system failure or restart. |
| Prefetch | Any int ?? | Refers to how many messages a consumer can receive before processing them. |
| Threads | Any int ?? | Refer to the parallel processing capability of a consumer to handle messages simultaneously. |
Endpoint and Listener Configuration
| Field | Supported Values | Description |
|---|---|---|
| Authentication method | Basic / OAuth2 | Specifies the type of authentication used by the API we want to call. |
| User | Any string | Refers to the user identifier used for authenticating API requests in Basic authentication. It typically represents the user's login credentials. |
| Password | Any string | In Basic authentication refers to the user's secret authentication code or password used alongside the username for API authentication purposes. |
| Client id | Any string | In OAuth2 authentication is a unique identifier assigned to the client application during the registration process with the authorization server. It is used as part of the OAuth2 protocol to authenticate the client application. |
| Grant type | password/client_credentials | If grant type is password, you need to specify user and password in addition to client id. If grant type is client_credentials, you must add the client secret. |
| Client secret | Any string | In OAuth2 is a confidential identifier known only to the OAuth2 client and authorization server. |
| Token url | Any string | In OAuth2 refers to the endpoint URL where the client application can exchange authorization codes or client credentials for access tokens with the authorization server. |
| Jira API url | Any string | URL to the Jira API. |
| Project | Any string | Project where the tickets we want to receive are located. |
Version compatibility
This functionality starts working from version 4.1.5 of 1Gateway.