Bugzilla – Full Text Bug Listing
| Summary: | [activity] add compensation/adjustment to elapsed time | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Robert Elves <robert.elves> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | cbeams, exceptione, jimisola, jmsalk, jokester01au, rolf, scot.morgan, Tom.Talbott |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Robert Elves
This is a good idea, and I think that the simplest thing (just adding the column) should be enough until we get additional user feedback. As part of this, we should also provide a tooltip that describes the mechanism for collecting the elapsed time. Upon initial activation tasks aren't accumulating time. (In reply to comment #3) > Upon initial activation tasks aren't accumulating time. ...is now fixed in head. Fixed up tooltip and label indicating how time is collected, rest will have to wait post 1.0. Mik, In the newsgroup four elapsed time cases were mentioned: 1. time while the task is active and eclipse open 2. time while the task is active and eclipse open, but user switched to for example browser or email 3. time while the task is active and eclipse open and frontmost only 4. time while the task is active and eclipse open and frontmost and there is activity in eclipse, so no time is accumulated after a certain period of inactivity I think that the behaviour should be configurable globally and possibly also on a per task basis. The reason for having it configurable on both levels is that I might choose 4 on a global level, but for a particular task I might know that I'll be using a text editor/shell/whatever and not Eclipse per-se. It would still, however, be nice to utilise Mylar and task/planning functionality. The "period of inactivity" should also be configurable and not hard-coded (to x minutes). Perhaps, this comment should result in a new enhancement request instead? (In reply to comment #6) I have seen some pretty strange times as counted by Mylar. This might be fixed in 1.0, but sometimes it counted 5-10 hours per week when I know for certain it should have been a lot more. Maybe the activity timeout was too short for me? Another developer got something like 80 hours per week (and no, he wasn't doing any overtime :)). (this should also probably a separate bug?) This time information doesn't seem very useful right now. We would like it to be useful enough so that the time spent info could be posted to the issue repositories (for example Changelogic allows that) and maybe even provide useful information for project managers. Personally, I would vote for 1. time while the task is active and eclipse open (either to replace the current system or as a separate "stopwatch") I read somewhere from Mik that the timings are based on the task activity history. If that could be exposed so that it was obvious when time was being automatically accumulated while allowing the user to add to or extend these time blocks, I feel that this would begin to be a useful feature. It seems to me that it could be done in a tabular form or a graphical form as long as there is a quick and easy way to adjust/add to it. My company is just starting to track time for various reasons, so I am now keenly interested in having this feature become usable. :) Yes, we do need to improve on the accuracy, and in particular on the predictability of the timing. Tom: the feature you are requesting is bug 147537, which is currently marked helpwanted, so post there if you are interested in exploring or contributing this feature. *** Bug 178727 has been marked as a duplicate of this bug. *** Task timing has been improved so supporting add/remove of time explicitly by user shouldn't be a problem now. Scheduling for 3.0 *** Bug 235250 has been marked as a duplicate of this bug. *** This is a planning or reporting tool specific feature, which we consider out of the scope of the core Mylyn project. Providing such an adjustment facility could involve considerably UI work, since adjustments may need to correspond to given days. If there is community interest in contributing this we could explore a contribution to the Sandbox in the upcoming Mylyn Incubator project (bug 214182). Mik, I'm not sure what you mean by "adjustments may need to correspond to given days", but all I'd like to be able to do is simply change the Active time for a task in case it needs to be adjusted. I don't need anything complicated or complex. For example, an icon/button next to it that, upon clicking, would bring up a simple free text form with 2 fields, allowing you to modify the number of hours and minutes, would do. Implemented like this, would it still involve "considerably UI work"? I'm also a Tasktop user. Would there be a better chance of this feature getting implemented sooner than later if I requested it through the Tasktop bug database? Thanks. Jeff: Mylyn will allow you to clear the active time, and we've limited the support to that. We tried to add more controls for active time to Mylyn (e.g. adding time), but found that this was not very useful without additional planning facilities. This is due to the fact that Mylyn tracks time via interaction events, so if you add time you are adding it at a given date, and you need to be able to see that. For example, if you added time last week, and you queried the time for the task this week, the time you added last week would not show up, which can be disconcerting. (In reply to comment #14) > I'm also a Tasktop user. Would there be a better chance of this feature getting > implemented sooner than later if I requested it through the Tasktop bug > database? We have to make this split between where to file enhancement requests more clear. We're in the process of updating the site for the 3.0 release, and I'll try to indicate which bugs should be filed against Mylyn and which should be filed against specific extensions of Mylyn. In general, you can file any bug against Mylyn in order to see if there is interest in such a feature. However, Mylyn committers only prioritize bugs that are within the scope of the project (http://wiki.eclipse.org/index.php/Mylyn/Plan/3.0#Scope ) unless we have clear indication of community resources to provide the contributions to contribute and maintain the feature being requested. So to answer your question, planning tools are out of the scope of Mylyn, and yes, Tasktop is providing planning extensions to Mylyn. I'll take a pass through the Mylyn Extensions page to indicate which tools provide which extensions to Mylyn: http://wiki.eclipse.org/index.php/Mylyn/Extensions Mik, how can one clear the active time in Mylyn? Is that a feature of an upcoming release? Mylyn 3.0 provides an "X" next to the Active time field. I don't recall whether this was added in time for Mylyn 2.3 or not. (In reply to comment #15) > Jeff: Mylyn will allow you to clear the active time, and we've limited the > support to that. We tried to add more controls for active time to Mylyn (e.g. > adding time), but found that this was not very useful without additional > planning facilities. This is due to the fact that Mylyn tracks time via > interaction events, so if you add time you are adding it at a given date, and > you need to be able to see that. For example, if you added time last week, and > you queried the time for the task this week, the time you added last week would > not show up, which can be disconcerting. Well, it is better than not having the possibility to adjust the time. If you completely rely on the mylyn time tracker, you should be able to correct time. It might be that you have forgotten to make a task active, and after 1 hour or so you realize that you worked without the time tracker. Can't you extend the domain of interaction events with one special event, such as: <InteractionEvent Delta="activated" EndDate="2008-04-26 18:08:01.171 CEST" Interest="1.0" Adjustment="+01:00" Kind="command" Navigation="" OriginId="org.eclipse.ui.workbench" StartDate="2008-04-26 18:08:01.171 CEST" StructureHandle="local-1" StructureKind="timeadjust"/> in case you do a time adjustment? *** Bug 250573 has been marked as a duplicate of this bug. *** *** Bug 325017 has been marked as a duplicate of this bug. *** 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 |