Bugzilla – Full Text Bug Listing
| Summary: | [activity] planner should only report time Elapsed during plan period | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> | ||||||
| Component: | Mylyn | Assignee: | Robert Elves <robert.elves> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P5 | CC: | mik.kersten | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Mik Kersten
With respect to the new planner design... I observed that the planning view we have discussed is just another representation of the task list. Perhaps we could make it a 'mode' of the current task list? This would eliminate the need for yet another view and keeps 'tasking' activity within the task view. This may be a potential extension point - view modes. The 'planning' mode would add a few new columns and group and sort tasks by week categories. Other than overloading the view, an immediate problem I see is that actual drag and drop to plan would be problematic, unless this was simply a static 'report' mode of view. Thoughts? That's a good point. Let's keep this in mind as we work out the history view. Created attachment 36782 [details]
Progress on time/logging issues.
Mik: This patch includes 'exploratory' changes for your consideration. In particular, changes to MylarContextManager to signal the timer upon context activation/deactivation. We still need a means of recording deactivation of active task upon shutdown.
Please re-generate this patch, too many conflicts. Created attachment 36852 [details]
Sorry, try this patch instead.
Patch applied. We need to make a close review of this together to make sure that timing is right, and set up additional tests if necessary, so I'll leave open until we can do that. Rob, is this still on for 0.6? Could get involved, moving to 0.7... *** This bug has been marked as a duplicate of bug 183826 *** |