GNOME Bugzilla – Bug 499090
Exported HTML have WRONG COST for co-worked tasks!!
Last modified: 2008-01-16 07:13:05 UTC
Please describe the problem: It's very important bug and it's almost killing me. I have to deliver the project plan to other people who doesn't use Gnome Planner, and I am shocked the cost had been wrong. For every project co-worked by many people, the cost is: cost = rate of people * number of people * number of people actually it should be: cost = rate of people * number of people I consider this a very serious problem, if the accountant didn't find such problem, the company lose money for this and people gets fired for such thing (because most tasks require more than one person here, which means ever project is double or triple cost. It is very important to fix this because this (export HTML) is the most used way users of gnome planner communicate their plan to the outside, and this communication deliver wrong message, this is not acceptable at all! Steps to reproduce: 1. create a task with two people, cost is 800.00 2. export to HTML, the cost become 1,600.00 3. someone gets fired. Actual results: exported HTML show cost for this task as 1,600.00 Expected results: exported HTML show cost for this task as 800.00 Does this happen every time? YES Other information: I cannot believe nobody reported this bug! They must have not been using Planner in real serious project planning otherwise they would be swearing in this bugzilla. From a user's prospective this bug can be even worse than planner crashed itself and bring down the gnome environment after burnt CPU and computer memory.
Created attachment 99513 [details] test document that exports incorrect cost in HTML
I just fixed this in the development version. If you want to try it out and don't know how to get planner from subversion, you can apply the following patch to /usr/share/planner/stylesheets/html1_tasks.xsl: http://svn.gnome.org/viewvc/planner/trunk/data/stylesheets/html1_tasks.xsl?r1=846&r2=870&view=patch If you know how to interpret a patch, you can also make the changes manually (it's only a small change). Thanks for reporting the problem!
I am sure it must be a small problem in regard to how many lines of code to update ! Thanks for fixing this, indeed it is a big problem for end user. I still remember I asked colleagues and me together to spent hours of time to re-fill cost things before sending it to upper level, luckily we didn't let the plan go as-is. I replaced my xsl and now it works fine!