-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 4.1.1, 5.0.1, 6.1.3, 6.2.7, 6.3.8, 6.3.15
-
Component/s: Issue - Actions
-
Environment:
Databases: Oracle
-
4.01
-
8
-
Severity 3 - Minor
-
1
Summary
Restarting Jira with the jira.clone.prefix value set to bank causes it to reset to the default value on Oracle databases
Environment
- Any supported Oracle database.
Steps to Reproduce
- Install Jira using Oracle database.
- Go to Jira Administration > System, General Configuration, button Advanced Settings (upper right corner) and modify the value of the jira.clone.prefix to a single space
- Restart JIRA
Expected Results
- The clone prefix key value remains as it was before the restart.
Actual Results
- The jira.clone.prefix key value is reset to "CLONE -"
Workarounds
- Using another of the supported platforms database.
- Create a file with the name "jira-config.properties" at JIRA_HOME and specifie the "jira.clone.prefix" property as follows:
jira.clone.prefix=
- An space can be indicated as the value instead of and empty value, which will be accepted and will not be reset after the restart.
Notes
- If the value is changed it will work as expected until the instance is restarted.
- In more recent versions (Jira 7.11+) Jira will not accept empty as a valid value and will instead revert to the default "CLONE -" immediately.
- relates to
-
JRASERVER-65137 Unable to clear the Clone prefix while using Oracle Database
-
- Closed
-
- mentioned in
-
Page Loading...