-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 7.2.8, 7.3.4
-
Component/s: System Administration - General Configuration
-
7.02
-
3
-
Severity 3 - Minor
-
1
Summary
JIRA Administrators are unable to set an empty clone prefix when using an Oracle Database.
Environment
- JIRA Server (tested in 7.2.8 and 7.3.4)
- Oracle 12c
Steps to Reproduce
- Open JIRA's Advanced Settings
- Edit the Clone prefix, removing the original 'Clone -' and leaving it empty.
Expected Results
You are able to set an empty value in the field
Actual Results
When you click on update, the value will return to the original 'Clone -'.
Notes
Similar to JRASERVER-27664
Workaround
Create or edit the jira-config.properties located in the JIRA-HOME and add the following value:
jira.clone.prefix=
This will set the value to the clone prefix to empty.
- is related to
-
JRASERVER-27664 Setting jira.clone.prefix to blank is reset to the default value upon restart on Oracle databases
-
- Gathering Impact
-