# Jira Account Settings and Cluster Settings
**URL:** https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [December 12, 2018, 9:06pm UTC](https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622 "2018-12-12T21:06:19Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Micah\_Hunsberger](https://discuss.elastic.co/u/Micah_Hunsberger)
#### Post date: [December 12, 2018, 9:06pm UTC](https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622/1 "2018-12-12T21:06:19Z")
I discovered a weird behavior with the jira settings in elasticsearch 6.5.x. It seems if you have them enabled in the elasticsearch keystore, then you cannot update the cluster settings.
All I have is a standalone elasticsearch node with trial license enabled.
If I add a jira account by using the instructions outlined here: [https://www.elastic.co/guide/en/elastic-stack-overview/6.5/actions-jira.html#configuring-jira](https://www.elastic.co/guide/en/elastic-stack-overview/6.5/actions-jira.html#configuring-jira)
```auto
/usr/share/elasticsearch# bin/elasticsearch-keystore list
keystore.seed
xpack.notification.jira.account.monitoring.secure_password
xpack.notification.jira.account.monitoring.secure_url
xpack.notification.jira.account.monitoring.secure_user
```
now if I execute this command:
```auto
curl -XPUT "http://localhost:9200/_cluster/settings" -H 'Content-Type: application/json' -d'
{
"persistent": {
"cluster": {
"routing": {
"allocation.enable": "none"
}
}
}
}'
```
I get this response
```auto
{
"error": {
"root_cause": [
{
"type": "illegal_state_exception",
"reason": "setting [xpack.notification.jira.account.monitoring.secure_user] is not dynamic"
}
],
"type": "illegal_state_exception",
"reason": "setting [xpack.notification.jira.account.monitoring.secure_user] is not dynamic",
"suppressed": [
{
"type": "illegal_state_exception",
"reason": "setting [xpack.notification.jira.account.monitoring.secure_url] is not dynamic"
},
{
"type": "illegal_state_exception",
"reason": "setting [xpack.notification.jira.account.monitoring.secure_password] is not dynamic"
}
]
},
"status": 500
}
```
I did not have this issue in 6.3.0, and it happens for any attempt to set cluster settings. If I remove the `xpack.notification.jira.*` settings from the keystore, there is no issue
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [December 13, 2018, 1:18pm UTC](https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622/2 "2018-12-13T13:18:08Z")
this indeed looks like a bug. we will investigate
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [December 17, 2018, 1:03pm UTC](https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622/3 "2018-12-17T13:03:59Z")
which Elasticsearch version are you using? Is it 6.5.3 or before that?
---
### Author:  [@Micah\_Hunsberger](https://discuss.elastic.co/u/Micah_Hunsberger)
#### Post date: [December 17, 2018, 1:59pm UTC](https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622/4 "2018-12-17T13:59:49Z")
I experienced it with both 6.5.3 and 6.5.2. the more controlled set up I described here was 6.5.2
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 14, 2019, 2:00pm UTC](https://discuss.elastic.co/t/jira-account-settings-and-cluster-settings/160622/5 "2019-01-14T14:00:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.