Bugzilla – Full Text Bug Listing
| Summary: | Filter read tasks | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Tomasz Zarna <tomasz.zarna> |
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | wmitsuda |
| Version: | dev | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tomasz Zarna
Tomasz, have you tried to use "Focus on Workweek" in the task list? It shows tasks scheduled for the current week, but also provides guaranteed visibility for new tasks and tasks with incoming comments. No, I've not. And at the first look it seems to exactly what I'm looking for! I've seen the option before, but I wasn't aware it has something to do with incoming/new tasks too. Thanks for the tip Eugene! In this case should we mark the bug as INVALID? Let's see what Mik will have to say on this. It seems like there is a discoverability issue for this feature and I can't find it documented in the user guide. It is only briefly mentioned in Mik's article at http://www.ibm.com/developerworks/java/library/j-mylyn1/#N103B5 See also this bug, if interested: 177208: provide a presentation that focuses on incoming https://bugs.eclipse.org/bugs/show_bug.cgi?id=177208 I've been using the "focus on workweek" to fit my needs for incoming tracking, but I have some complaints regarding the enforced sorting of elements (bug#217531, bug#217530). The problem I see is that we are using "focus on workweek" as a workaround for the lack of a dedicated "focus on incoming". But workweek mode is for personal planning. It does not fit well if you just want to monitor some inbox (like I do for some eclipse.org projects). What I need is an flexible replacement for bugzilla email notifications. One solution is to eliminate some constraints in workweek mode. Another solution would be to add another dimension to task list, orthogonal to task presentation; We may call it "sorting and filters", where "focus on workweek" is one of them, and "focus on incoming" is another. Thomasz: as you use it, please let us know how well focus on workweek meets your needs. Eugene: yes, I have serious concerns about the discoverability of the Focus button and have created bug 219365 to discuss alternatives. Willian: Focus on Workweek is intentionally a mix of incoming and scheduling, based on the theory that both are involved in our decisions on what task we should do next. The key thing with Focusing of any view is that we make it orthogonal to the presentation. This means that the user can focus their Task List whether they're in the Categorized or Scheduled presentation. I agree that we should continue to explore a presentation or other mechanism that focuses more on incoming. Let's discuss further on the bug 177208. (In reply to comment #2) > In this case should we mark the bug as INVALID? Tomasz: please comment on this or the other bugs linked if you have further feedback on how this feature works. And sorry for putting an "h" in your name in comment#5, you'd think I wasn't Polish ;) (In reply to comment #5) > Eugene: yes, I have serious concerns about the discoverability of the Focus > button and have created bug 219365 to discuss alternatives. Mik, please note that it wasn't about discoverability of the "focus on workweek" itself (which I think many users simply don't understand), but discoverability of the guaranteed visibility of new changes when "focus on workweek" is on. > This means that the user can focus their Task List whether they're in the > Categorized or Scheduled presentation. It doesn't seem like Scheduled presentation provides guaranteed visibility for incoming changes, so you can't use convenience of that presentation for scheduling these tasks. As Willian I also think that it still can be useful to not see these incomings as they are usually distracting. The problem with splitting incoming and scheduling info into two separate presentations is that we would require users to switch presentations much more frequently. We currently have a way of getting rid of the incomings: switch into the Scheduled presentation. There are definitely the tradeoffs that Willian mentions that I think we should continue to consider, but I don't think it's clear yet whether splitting out how guaranteed visibility works in the standard presentation would help sufficiently. I think we should first try to create a good Incoming presentation if we can, and then consider removing some of the functionality of the current Focused mode of the Categorized presentation. Future points on incoming-related discussion should go on bug 177208 so that we don't lose track of them. (In reply to comment #6) > Tomasz: please comment on this or the other bugs linked if you have further > feedback on how this feature works. And sorry for putting an "h" in your name > in comment#5, you'd think I wasn't Polish ;) No problem, I'm used to it. Nobody's perfect ;) (In reply to comment #7) > Mik, please note that it wasn't about discoverability of the "focus on > workweek" itself (which I think many users simply don't understand), but > discoverability of the guaranteed visibility of new changes when "focus on > workweek" is on. Exactly. I knew there such thing as "Focus on Workweek", I simply didn't realize it filters new/incoming tasks too. Here is what I've observed while working with the option turned on: 1. I've got this "automatic container" called "Unmatched" in my Task list. In my case it's huge (over 900 tasks), majority of them in incoming or new. The problem is that even if I collapse it, then open a task from a different query and then open the task list again the "Unmatched" container expands again. It's quite annoying and pollutes the tasks list with useless information. I could mark all the tasks from the container as read but that's not my point. 2. Queries with incoming/new tasks are missing the => icon while in the workweek mode. But you probably have bug for it already. 3. Suppose that there is a new task in the list. I open and activate it. When done working if it, I deactivate it. Then, it will disappear from the task list. If I want to work again with that task (and I haven't schedule it) I need to turn off the "Focus on Workweek" option (or use the "Find" query field if I remember it's summer or number). What about using a context on task list itself, so the tasks which has been activated during current week are visible in the list. 4. Finally, what I'm missing here is an ability to schedule a query. I have couple of queries which are tidily coupled with Eclipse's milestones. I must admit I'm not scheduling individual tasks while working with Mylyn, but such option for queries would be vary handy in my case. Do any of these sound reasonable? (In reply to comment #7) > As Willian I also think that it still can be useful to not see these incomings > as they are usually distracting. I'm not questioning whether showing incomings in workweek mode is good or bad. My complaints are that workweek mode is today the only workaround to monitor incomings in a huge task list, and it has issues on that context. (In reply to comment #9) > 2. Queries with incoming/new tasks are missing the => icon while in the workweek > mode. But you probably have bug for it already. Apparently there are some inconsistencies about when/on what the incoming icon is displayed for task containers in both modes. Tomazs, please read bug#216053 comment#5 and forth. Mik, could you comment on bullets 1., 3. and 4. from comment 9? Should I log separates bugs for them? Or are they out of your scope at the moment? Tomasz: sorry for the very slow reply. > 1. I've got this "automatic container" called "Unmatched" in my Task list. In my > case it's huge (over 900 tasks), majority of them in incoming or new. The > problem is that even if I collapse it, then open a task from a different query > and then open the task list again the "Unmatched" container expands again. It's > quite annoying and pollutes the tasks list with useless information. I could > mark all the tasks from the container as read but that's not my point. Mylyn works much better when the Unmatched container is cleaned up. I documented this, and ways to clean up, at: http://wiki.eclipse.org/Mylyn/FAQ#Why_do_tasks_appear_in_the_Unmatched_container.3F > 2. Queries with incoming/new tasks are missing the => icon while in the workweek > mode. But you probably have bug for it already. This is by design. When focused the Task List maintains expansion state, so the decorations are redundant. > 3. Suppose that there is a new task in the list. I open and activate it. When > done working if it, I deactivate it. Then, it will disappear from the task list. > If I want to work again with that task (and I haven't schedule it) I need to > turn off the "Focus on Workweek" option (or use the "Find" query field if I > remember it's summer or number). What about using a context on task list itself, > so the tasks which has been activated during current week are visible in the > list. Yup, which is why any tasks that should be worked on either need to be scheduled, e.g. for This Week, meaning that you intend to activate the task again this week. Alternatively, you can use the task activation history (top right of Task List). > 4. Finally, what I'm missing here is an ability to schedule a query. I have > couple of queries which are tidily coupled with Eclipse's milestones. I must > admit I'm not scheduling individual tasks while working with Mylyn, but such > option for queries would be vary handy in my case. We don't consider queries something that you can work on and activate, they are just containers that inherit the scheduled state of their children. This is important sine it prevents them from showing if they have no tasks scheduled. For example, I have close to 100 queries, but not more than a dozen show at any time. |