Community
Participate
Working Groups
Sometimes you are added as cc in some task because someone wants to bring you attention (like just happened to me in bug#219171). But the problem is that I already am subscribed into some query that includes that task. We need some visual indication in task list to emphasize incoming tasks that are directed to you, regardless of you were already monitoring it, where "directed to you" would mean: - You were added as cc. - You were assigned to it. - You were assigned to QA. Maybe a simple indication like a double dark blue arrow, instead of the traditional light blue arrow, should work.
It should work for new unread incoming tasks as well.
One problem with this is that notification would need the task data in order to retrieve this information, but task data currently don't have common schema that would provide something like that (in other words it is connector-specific).
We usually recommend that you organize your queries in a way that makes this explicit (e.g. a separate query for all tasks assigned to you), but I see your point.
Actually I have this. For example, here I have one query which catches all Mylyn bugs in which I'm reporter/assignee/cc. Also have another one to catch mylyn-inbox. The problem is when I read something from mylyn-inbox, and later I got cc'd to comment about some detail. In this case, on next sync that task will be caught by the other query, but: 1 - It will appear as an updated task, so you cannot rely on "new unread task" icon to bring attention. 2 - It will appear mixed with all other tasks I'm reporter/assignee/cc which I may prefer to read later when I have more time. It is not unusual for me to read something I'm interested and NOT cc myself. Usually when this happens it is because I want to do some research before commenting/cc. On these cases, I normally mark them unread so when I have more time to do a full task list pass I don't forget to reply.
We can consider a UI design that would make this more clear for 3.1.
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
