Community
Participate
Working Groups
1. When using working sets, the tasklist can be empty, although there are problems in "related" projects. If I assume that the empty (filtered) tasklist means that I have addressed all of the problems, I can release code that breaks other components in the workspace. The filtering notification is subtle (shows NNN out of MMM, but doesn't draw "graphical" attention to the fact that something may be amiss). 2. When the tasklist is not visible (because it is behind the console, for example), then I cannot tell that tasks have been added to it. The following mechanism may address this issue: the tasklist tab graphically shows that the tasklist (a) has contents and (b) has changed contents (This is related to bug 37032)
With the new problem filtering and limit features, do we still know how many errors/warnings/infos are outside of the filtered set? In other words, does the processing still continue in background, or do we not even gather stats on the excluded projects/resources? I'm curious about just what indications can be given for problems outside the selected scope. Thanks.
There are currently no plans to work on this feature
