Community
Participate
Working Groups
When I first set up Mylyn, I found the Task List view and the Task Repositories view. So I added some repositories - that was easy. But no tasks showed up in the Tasks List view. I added some categories, but still no joy. I finally figured out that I needed to create queries - of course that makes sense (how else would it work?), but the introductory user interface isn't clear that I need to do that. There is no obvious flashing light pointing me to "create a query to see what is in a repository". Perhaps if the Task Repository view showed all the queries defined for that repository? And if there were none it might show "define a query for this repository"? Something like that?
Bjorn, you may want to try Mylyn 2.1M1. I believe we added special support for exactly this use case. So, you'll get a dialog asking you you'd like to create query right after task repository wizard is completed. Mik, it seems like we missed this feature in the New and Noteworthy, so as new features for exporting tasks and queries. Though the latter may still need some polishing.
Eugene: yup, I excluded this from the New & Noteworthy because it seemed too minor. Bjorn: as Eugene indicates, we now have this prompt in-line with the wizard workflow of new repository creation. It seems to me that this is prominent enough, but please comment or reopen if you think that it should be made more prominent elsewhere in the UI. We also have a "New Query" action on the context menu of the Task Repositories and Task List views, but alone they are not discoverable enough. We are still considering re-adding the New Query button to the toolbar, but that's pretty expensive real-estate which is why it is no longer there. *** This bug has been marked as a duplicate of bug 174473 ***
Created attachment 78306 [details] prototype of queries and lack of queries showing in task repository browser I imagine something like this, showing that there are four queries for one of my repositories and none for the other. Then it is very obvious to me why none of the tasks from that other repository are showing up in my task list. Just a thought.
It is somehow weird to show queries in the repository view. Especially because individual repository tasks can be added to the task list without creating query, or they could retain in the Archive category after query is deleted. However it would be useful to add "New Query..." and other actions to the view toolbar (the same ones we have in the popup menu).
(In reply to comment #4) > It is somehow weird to show queries in the repository view. We each have our own opinion :-) I don't see it as weird at all, because I see the objects involved as a network rather than two separate lists. Repository objects --refer to--> Query objects Repository objects --refer to--> Task objects Query objects --refer to--> Repository objects Query objects --refer to--> Task objects Task objects --refer to--> Repository objects etc. Thus a list that shows: Repository Query makes perfect sense to me. Or even: Repository Query Task or: Query (Repository) Task and so on.
Right. The weirdness I was referring to is that it won't make sense to show queries under repository nodes and not show tasks. On the other hand, showing tasks there don't make much sense, because it would make repository simply too crowded and will practically duplicate Task List UI. There also was an idea that connectors could contribute content providers to the task repository, i.e. to show project structure (projects, components, etc). We could probably add special presentation mode for Task List view that would show repositories at the root and then all tasks from those repositories, perhaps grouped by query/category node (sort of reversed variant of current "grouped by repo" presentation from sandbox).
Bjorn: I agree with your nice summary on comment#5 and the screenshot. The split that we have made for Mylyn is to have one very simple list UI for task repository configuration (very infrequent operation), and a separate and much more sophisticated UI for task management (very frequent operation), and then to link the two via a context menu in the Task Repositories view. But the Task Repositories view is not designed to be visible in a typical working perspective. Given this split (which could also be up for debate) are you interested making the Task Repositories view more of a view for task/query management, or in making repositories more primary in the Task List? I worry that if we add query nodes to the Task Repositories view users will then want to see tasks under them, and then we have two views with the same responsibility (task/query management and navigation).
(In reply to comment #7) > Given this split (which could also be up for debate) are you > interested making the Task Repositories view more of a view for task/query > management, or in making repositories more primary in the Task List? I don't know. I was just thinking about new users (like I was). I add a Task Repository but still nothing shows up in the Task List. Should they just all show up by default, I think to myself. (Obviously not, for sheer bandwidth issues.) And then I wonder "how to get those tasks I know I have in the repository to show up in the Task List?" It's not immediately obvious (at least not to me) that a query is the way to do that. Maybe when you add a repository it should ask for queries right away? So as to make the connection in people's minds? I don't have a great answer - I'm just sort of thinking out loud here. > I worry > that if we add query nodes to the Task Repositories view users will then want > to see tasks under them, and then we have two views with the same > responsibility (task/query management and navigation). I understand that concern (and it's a valid one).
(In reply to comment #8) > Maybe when you add a repository it should ask for queries right away? So as to > make the connection in people's minds? I don't have a great answer - I'm just > sort of thinking out loud here. Your thinking aloud is always appreciated :) What you're asking for here will be available with the upcoming 2.1 release and should address the new user experience problem by prompting them into the new part of the UI (this was bug 174473). We'll keep an eye out for how much that helps with the initial confusion. One thing it doesn't do is show people that they can use the context menu in the Task Repositories view, but at least now they will get taken straight to the Task List. We may also add a New Query button to the Task List toolbar since the context menu is not as discoverable.
