Issue Details (XML | Word | Printable)

Key: JRA-6904
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Mick Hollins
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Upgrade from 3.1.1 to 3.2 breaks time estimates

Created: 06/Jun/05 12:06 AM   Updated: 30/Jul/06 07:37 PM
Component/s: Import / Export
Affects Version/s: 3.2
Fix Version/s: 3.2.1

Time Tracking:
Not Specified

Issue Links:
Blocker
 
Duplicate
 

Participants: Anton Mazkovoi [Atlassian], Dylan Etkin [Atlassian], Mick Hollins and Scott Farquhar [Atlassian]
Since last comment: 3 years, 25 weeks, 6 days ago
Resolution Date: 07/Jun/05 12:13 AM
Labels:


 Description  « Hide
In upgrading from 3.1.1 (by exporting and importing) my estimates have been erroneously shortened. For example, a task which had an estimate of "4 days" in 3.1.1 now has an estimate of "1 day 8 hours" in 3.2.

I believe this stems from the fact that in Jira 3.1.1 I have set weeks to be 5 days, and days to be 8 hours. It looks like the import has ignored that fact and used 24 hour days to convert 115200 seconds to 32 hours and then to "1 day 8 hours", rather than converting it to "4 days".

If I check "Administration .. Time Tracking", my 3.2 installation is correctly set to 8 hour days.

One other thing that may be relevant is that I am exporting from a Jira 3.1.1 that is using SQL Server, and importing into a Jira 3.2 that is using hsqldb.

I've raised this as a "Blocker" as it is preventing us upgrading to 3.2, but I'll understand if the Atlassian folks downgrade it somewhat. Especially if they can provide me with a workaround.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] added a comment - 06/Jun/05 03:17 AM
Mick,

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?


Mick Hollins added a comment - 06/Jun/05 04:04 AM
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).

Mick Hollins added a comment - 06/Jun/05 04:10 AM
For the sake of completeness, I've found that the estimates are rendered correctly in the following views:
  • Full Content
  • the issue view (i.e. the one you get by clicking on the issue).

and incorrectly in the following:

  • printable
  • excel
  • XML

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,
mick


Anton Mazkovoi [Atlassian] added a comment - 06/Jun/05 11:17 PM
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,
Anton


Dylan Etkin [Atlassian] added a comment - 07/Jun/05 12:13 AM
All the views now display the estimates in a format that respects the day and week length settings.