# Issue Integrating Elasticsearch with JIRA REST API
**URL:** https://discuss.elastic.co/t/issue-integrating-elasticsearch-with-jira-rest-api/102616
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [October 3, 2017, 9:16pm UTC](https://discuss.elastic.co/t/issue-integrating-elasticsearch-with-jira-rest-api/102616 "2017-10-03T21:16:20Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Olatunde\_Tokun](https://discuss.elastic.co/u/Olatunde_Tokun)
#### Post date: [October 3, 2017, 9:16pm UTC](https://discuss.elastic.co/t/issue-integrating-elasticsearch-with-jira-rest-api/102616/1 "2017-10-03T21:16:21Z")
Hello,
Im configuring watcher to create tickets using JIRA rest api. Our JIRA API is not hosted on the default path, and this causes and error in the watcher action. (watcher cannot find the rest api).
The default JIRA path to create tickets is: [https://devEnv.com:443/rest/api/2/issue/](https://devEnv.com:443/rest/api/2/issue/)
Our JIRA path is: [https://devEnv.com:443/AppServer/rest/api/2/issue/](https://devEnv.com:443/AppServer/rest/api/2/issue/)
I get the following errors when the watcher triggers.
```
"reason": "Not Found (account uses invalid JIRA REST APIs) - Exception when parsing jira response [com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@3e456b9b; line: 1, column: 2]]\n",
"request": {
"host": "https://devEnv.com",
"port": 443,
"scheme": "https",
"method": "post",
"path": "/rest/api/2/issue",
"headers": {
"Content-Type": "application/json; charset=UTF-8"
},
"auth": {
"basic": {
"username": "jira_account"
}
},
```
Is there a path variable that can be used to specify the path on this action?
```
"actions": {
"create-jira-issue": {
"throttle_period_in_millis": 3600000,
"transform": {
"script": {
"stored": "transform"
}
},
"jira": {
"account": "jira_account",
"fields": {
"issue": {
"summary": "Some devices have not sent logs to Elastic",
"issuetype": {
"name": "Bug"
},
"project": {
"key": "MON"
},
"description": "Device Monitoring: Systems not responding in the last {{ctx.metadata.last_period}} minutes:{{#ctx.payload._value}}{{.}}:{{/ctx.payload._value}}",
"priority": {
"name": "High"
},
"labels": [
"auto"
]
}
}
}
}
```
},
Config files looks like this:
```
xpack.notification.jira:
```
account:
monitoring:
url: [https://devEnv.com:443](https://devEnv.com:443)
user: jira\_account
password: xxxxxxxxxxxxxx
issue\_defaults:
project:
key: MON
issuetype:
name: Bug
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [October 11, 2017, 7:37am UTC](https://discuss.elastic.co/t/issue-integrating-elasticsearch-with-jira-rest-api/102616/2 "2017-10-11T07:37:38Z")
This is indeed a bug and will be fixed in one of the future versions of Elasticsearch, where we will allow you to specify a concrete URL as endpoint where a JIRA issue gets sent to.
---
### Author:  [@Olatunde\_Tokun](https://discuss.elastic.co/u/Olatunde_Tokun)
#### Post date: [October 11, 2017, 3:56pm UTC](https://discuss.elastic.co/t/issue-integrating-elasticsearch-with-jira-rest-api/102616/3 "2017-10-11T15:56:27Z")
Thanks for your feedback Alex!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 8, 2017, 3:57pm UTC](https://discuss.elastic.co/t/issue-integrating-elasticsearch-with-jira-rest-api/102616/4 "2017-11-08T15:57:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.