After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 580216 - Maximum percent complete is 75%
Maximum percent complete is 75%
Status: RESOLVED FIXED
Product: planner
Classification: Other
Component: General
0.14.x
Other All
: Normal normal
: ---
Assigned To: planner-maint
planner-maint
: 615289 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-25 13:49 UTC by Aecio F. Neto
Modified: 2010-04-09 14:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aecio F. Neto 2009-04-25 13:49:38 UTC 
Please describe the problem:
The complete percentage is being set as 75% only, when 100% is entered.
Any value below 75% is kept properly though.

Steps to reproduce:
1. Create a task
2. Open tasks properties
3. Set percentage to 100% complete
4. Confirm change
5. Open tasks properties again and it will be set as 75%


Actual results:
As mentioned

Expected results:
percent complete to keep entered value, from 0 up to 100

Does this happen every time?
Yes

Other information:
Comment 1 Srikant 2009-05-26 06:50:54 UTC 
When dragging inside a task block to indicate percentage completion, the gray band covers the entire width of the task block, but task properties still shows 75%.
There's another report on this that said the problem went away after a fresh install of Fedora.
(http://markmail.org/message/nrlcrda7n2v4jpsr#query:gnome%20planner%20task%20completion%2075%25+page:1+mid:vt42qwjvlvghbviq+state:results)
Comment 2 Maurice van der Pot 2009-06-29 20:24:04 UTC 
As a temporary fix for anyone who is running into this at the moment,
one can modify one line in the following file:

  <INSTALLDIR>/share/planner/glade/task-dialog.glade

Line 236 should be changed from:
  <property name=3D"adjustment">0 0 100 10 25 25</property>
to
  <property name=3D"adjustment">0 0 100 10 25 0</property>


Anyone using the priority field should also change line 257 from:
  <property name=3D"adjustment">0 0 9999 1 10 10</property>
to
  <property name=3D"adjustment">0 0 9999 1 10 0</property>
Comment 3 Maurice van der Pot 2009-10-30 21:55:14 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 4 Alexandre Franke 2010-04-09 14:01:22 UTC 
*** Bug 615289 has been marked as a duplicate of this bug. ***