View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0006915mantisbtadministrationpublic2006-04-05 05:062013-02-08 16:39
ReporterStefanPapp Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product Version1.0.1 
Summary0006915: Estimate time and effort
Description

For release planning, it is always important to know about the estimated time and effort of issues. Every developer can guess roughly how much time he will need to fix one or another issue or to implement a new feature in case they can fully concentrate on them. Very often, it will be decided then, if this or that feature will be included into an release.

My proposal:
Provide a field "estimated effort" that can be set to get an idea how long it will take to fix an issue. I guess, good parameters would be

  1. "Within one hour"
  2. "Within half a day"
  3. "Within a day"
  4. "Within three days"
  5. "Within a week"
  6. "Within two week"
  7. "Within a month"
  8. "Longer than a month"
TagsNo tags attached.

Activities

tmhoefer

tmhoefer

2010-08-04 05:04

reporter   ~0026209

I think it is more practicable to enter only the estimated time in hours than select from a predefined list.
squarebox

squarebox

2010-09-06 20:35

reporter   ~0026602

in Mantis 1.2.2 this could be easily done via custom fields.

While something completely different, the latest mantis also has time tracking built in (primarily for helpdesk usage i would presume) to automatically monitor how long have been working on a bug.

My current implementation actually has a custom field to track how long it actually took to complete the bug.
rca

rca

2012-06-01 05:10

reporter   ~0031945

As squarebox said, MantisBT custom fields is the feature to be used. As example, you may check our Workload Plugin : https://github.com/embedia/mantisbt_workload