Bugzilla – Full Text Bug Listing
| Summary: | [planning] allow default estimated time to be set for local tasks | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P2 | CC: | david.shepherd, robert.elves |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Sun | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Eugene Kuleshov
This was done deliberately in order to make estimation come for free without the user needing to always remember to estimate each task, just to adjust down to 0 for some tasks, and higher than 1 for others. In other words, to make the XP-style planning practice Kent Beck advocates easy. That said, there is no single right answer for this so we almost certainly need a preference setting. Marking P2 for now because post-1.0 the planning support needs to be come more configurable. I would agree that it is always makes sense for local tasks, but very unlikely needed for repository tasks. However that timing could screw up your non-disableable never green bar, if those new repository tasks scheduled for reasons other then working on them (i.e. reminder for a follow up)... More precisely it doesn't make sense for repository tasks that you create for others, but does make sense for repository tasks that you create for yourself. We still need to support both modes, and perhaps there are cases where we detect. For example, "Report as Bug" in the Error Log should clearly not schedule for today. However, even in this case scheduling can still make sense. For example, I schedule each bug report that I report to Eclipse for 2 weeks later so that I follow up on it. One thing we could do to make the UI easier is have a radio chooser along these lines. Schedule for: [never] [today] [next week] [two weeks] [custom date [pick...]] Mik, I would say that most of the repository bugs are not created for "yourself". What we can do there is to allow to specify tentative assignment for created bug (even server does not allow that you could make second call to reassign issue to yourself after it is created). Default choice would rely on server side logic, but you can choose to assign it to youself (we can make editor to remember last choice), then estimate could be set to default. Please don't use radio buttons for scheduling it will eat up lots of screen space. I think current selection is optimal. It is compact and most of the time I am using Clear on it (and suspect that most users should do the same when filling bugs for others). Though that date drop down could show the same menu as in task list, and have actual data selection dialog as one of the options in that menu. Rob: I think that there's another bug for this, related to making the scheduling/estimate sticky per repository. We need to work out what to do with estimated times for 3.2, even if this isn't the solution. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |