| templateType | template |
|---|
| templateOption | {"label":"Knowledge Base Template v4 Cloud Migration Ready","value":"975385006470811132","templateType":"template"} |
|---|
| templateTypeOption | {"label":"Confluence template/blueprint","value":"template"} |
|---|
| templateId | 975385006470811132 |
|---|
| excerpt | Summary Jira will sometimes not display Salesforce associations that were recently created. This is usually caused by latency and related issues with the "Affected Versions" field values. The underlying cause is usually the “session stickiness” setting is not correctly configured in the Data Center environment. Environment JIRA version 8.11.1 and prior releases Diagnostics Steps Not applicable. Cause We have found i ndex replication lag can occur between multiple nodes, in which the create request was first sent to node A , followed by the fetch request sent to node B , just before the changes on node A get replicated onto node B. This situation is also stated by Atlassian as one of the common problems using DC. Workaround We currently have tested both workarounds below and they have helped Workaround 1 Please configure session stickiness on your load balancers based on Atlassian’s documentation . Workaround 2 Please ensure that you update to Jira 8.12.0 and above, as Jira has introduced Document Based Replication which helps to speed up replication across multiple nodes. Restart Jira server and clearing all browser related cache usually is a good practice when working with cache related updates. Do ensure these are completed as well. Resolution Not applicable. |
|---|
| fieldGroupKeys | {"2y3hhobuup":["net.customware.confluence.plugin.scaffolding__2y3hhobuup__data_0_bj69jg0n6d"]} |
|---|
|