AWS Thinkbox Discussion Forums

monitor pool filtering error

Seems the primary/secondary pools might not be respecting filters properly:

deadline_pool_filter_error.jpg

Thanks for catching that. In beta 9, we’ll be adding a Secondary Pool column and giving it it’s own quick filter list so that it works properly.

Cheers,

  • Ryan

I would actually probably prefer if there was only one pool quickfilter option, but it worked for both primary / secondary pools. So if the checked pool shows up in either field , the job is displayed.

What’s the opinion of others on this? Maybe im alone with that :slight_smile:

We had tried that approach, but the issue is that we currently use the existing filtering system, and whenever an item is unchecked, we add a “does not match” filter item. So even with using regular expressions, if you unchecked the “2dshared” pool for example, but still had the “2d” pool checked, the jobs with “2dshared / 2d” would still get filtered out. Technically, this is correct, since you are telling the system “I don’t want to see 2dshared jobs”, but feels backwards from a usability point of view.

By having a separate quick filter for the secondary pool, you get a little more flexibility.

Privacy | Site terms | Cookie preferences