MantisBT - v2.4 Release (Closed) |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000515 | v2.4 Release (Closed) | [All Projects] General | public | 2010-07-21 06:15 | 2011-08-16 23:48 |
|
| Reporter | caseydk | |
|---|
| Assigned To | caseydk | |
|---|
| Priority | normal | Severity | feature | Reproducibility | have not tried |
|---|
| Status | closed | Resolution | fixed | |
|---|
| Platform | | OS | | OS Version | |
|---|
| Product Version | | |
|---|
| Target Version | | Fixed in Version | 2.4 | |
|---|
|
| Summary | 0000515: Detailed percent complete tracking |
|---|
| Description | At present, the Task's percent complete is on the Task (and tasks table) itself. While this makes loading the Task View easy, it also makes it so that we lose the progression over time.
For example, if I update it from 0 to 50% on Monday and then to 95% on Friday and then JoeBob updates it to 55% after me, then it's 55% complete. It could be a simple oversight where I hit "save" before him, but there's no record of who updated what when. |
|---|
| Additional Information | The solution I see is attaching the percent complete to the Task Log (on the task_logs table) which would connect it with a person and a timestamp. Then at the same time, duplicate the latest percent complete on the Task itself.
It's slightly denormalized but no worse than how it works on the projects table. |
|---|
| Tags | No tags attached. |
|---|
| Relationships | |
| Attached Files | |
|---|