avatar kthomas Sep 25. 2008. 7:27 pm
Because tasks do not map evenly to progress-- one ticket can take five minutes to complete, another 20 hours-- the progress bar is darn deceptive.

Moreover, our more, um, "unexperienced" clients may come into a project page after 100 tickets/tasks have been added, however minor, and suddenly see "24%" complete-- and then wonder "why's nothing getting done here???"

Other than CSS, we could use a way to turn this off at will. Please.
avatar kthomas Sep 26. 2008. 3:05 pm
Also, milestones are calculated into the progress bar results. As they only consist of the tasks they contain, this is counter-intuitive.

Also, we tend (strongly) to use milestones as containers: short-term, medium-term, long-term, out-of-scope. This means that these containers (always open) appear as "unfinished tasks" in the bar.