-
Bug
-
Resolution: Fixed
-
High
-
None
-
None
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
The downgrade checks to see if the downgrade build number in the XML file is the same as the build number you are downgrading from. We sync these up at release time, but if we do a point release that syncing can get lost. At the moment we have 5.2-m05.1 in JOD with a build number of 807. 5.1.4 has a downgrade allowed of 806 and 5.1.5 has a downgrade allowed of 808, neither of these match so we can't downgrade.
- relates to
-
JRACLOUD-29841 Releasing a point release milestone stops the downgrade from working
-
- Closed
-
-
JRASERVER-30213 Remove the need to start with a fresh database when restoring an OnDemand backup to latest available downloadable production version
- Closed
- copied from
-
JRADEV-15192 Loading...