The endpoint encapsulates portions of the JIRA API, relying on the jira-rest-java-client SDK. Available endpoint URIs include: CONSUMERS jira://newIssue (new tickets) jira://newComment (new comments on tickets) The endpoints will respond with jira-rest-java-client POJOs (Issue, Comment, etc.) Note: Rather than webhooks, this endpoint relies on simple polling. Reasons include: - concerned about reliability/stability if this somehow relied on an exposed, embedded server (Jetty?) - the types of payloads we're polling aren't typically large (plus, paging is available in the API) - need to support apps running somewhere not publicly accessible where a webhook would fail
| Name | Kind | Type | Required | Deprecated | Default Value | Enum Values | Description |
|---|---|---|---|---|---|---|---|
| type | path | org.apache.camel.component.jira.JIRAType | true | false | NEWISSUE NEWCOMMENT |
||
| serverUrl | parameter | java.lang.String | false | ||||
| username | parameter | java.lang.String | false | ||||
| password | parameter | java.lang.String | false | ||||
| jql | parameter | java.lang.String | false | ||||
| delay | parameter | int | false | 6000 | |||
| exchangePattern | parameter | org.apache.camel.ExchangePattern | false | InOnly | InOnly RobustInOnly InOut InOptionalOut OutOnly RobustOutOnly OutIn OutOptionalIn |
Sets the default exchange pattern when creating an exchange | |
| synchronous | parameter | boolean | false | false | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |