|
Actually, I just noticed something. It's only in the Issue Navigator that the estimate is wrong. When I click on the issue and go to the issue view, the estimate is fine. This would suggest that you are right and it is just a rendering problem in certain views (including the RSS view by the way).
For the sake of completeness, I've found that the estimates are rendered correctly in the following views:
and incorrectly in the following:
BTW: I take it that you don't really need me to check the before and after database values anymore as you now can be sure it is a rendering problem? cheers, Hi Mick,
Thanks for the info. We'll see if we can trace down the problem and fix it for 3.2.1 that should be released some time next week. Thanks, All the views now display the estimates in a format that respects the day and week length settings.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Can you look at the database, and let me know what the values are in the jiraissue table for the time estimates? They should be the same for both before & after the upgrade.
If that is the case, then it is just a rendering problem, where we probably aren't respecting the conversion amounts.
Can you let me know if the incorrect time estimate happens on all pages?