Affects Version/s: 2.3.1
Fix Version/s: 2.4
The change for
MPIR-171 added a check to see if the timezone is numeric. If not, it reports a warning.
However, the check fails to allow for non-integral timezones - e.g. 5.5 - and the warning message is incorrect, as it does not show the correct information.
For example, the following setting:
results in the warning:
[WARNING] The time zone '-2147483648' for the developer 'Name' is not a recognised time zone, use a number in the range -12 to +14 instead of.
The message should read something like:
[WARNING] The time zone '+5.5' for the developer 'Name' is not a recognised time zone, use a number in the range -12 to +14 or a valid long TimeZone id.
except that it should not be generated for that particular timezone, as +5.5 is as valid as +5 (which does not generate a warning).
1) the warning message is not helpful, as it does not show the correct timezone.
2) the warning should not be generated for fractional timezones.
|Field||Original Value||New Value|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||2.4 [ 17000 ]|
|Assignee||Herve Boutemy [ hboutemy ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Project Import||Sun Apr 05 12:10:01 UTC 2015 [ 1428235801085 ]|
|Workflow||jira [ 12723484 ]||Default workflow, editable Closed status [ 12755951 ]|
|Project Import||Mon Apr 06 00:45:01 UTC 2015 [ 1428281101090 ]|
|Workflow||jira [ 12961149 ]||Default workflow, editable Closed status [ 12998143 ]|