Details
-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
4.0.1
-
4
-
Severity 2 - Major
-
-
Description
Upgrade Tasks in JIRA are supposed to be idempotent - that is, if you have to run it multiple times (for whatever reason) then it should be able to execute each time and not screw up.
Currently, when an upgrade task adds an error as if to signal that the upgrade task did not complete successfully, it still creates the record in the UpgradeHistory table in the database. This means that in future, this task will be skipped because it is deemed to have already been run. This seems a bit counter-intuitive: if the task had an error, it would probably require re-running at some point after the error is corrected.