My goal for this plug-in was to create a view based on parms. In this view, I would see the passed/failed tests for my job builds with parm=x.

The filter works as intended and selects the job for the view because one of the builds used parm=x. However, I would like the view to include only builds where parm<>x.

When the view only include builds of parm=x, then I can see my tests passed/failed. As it is, the view is misleading because it is based on Jobs and not build details (like parm=x). My view is then reporting across different parms (environments) because of old builds.

I realize this is likely outside the scope of this plugin but I'll explain how this would help me and maybe others.

I have one job to execute tests that have parameters like ENV with values XYZ,123, or 999.

To track the passed/fail results, I need to create 3 Jenkins jobs for each environment. 

Instead of creating multiple jobs to track environment, I can create one job. Use that same job and execute for multiple parameters (XYZ, 123, 999).

If this plugin filtered builds, then I can create a 'view' for environment=XYZ and view my results for just XYZ. Another environment could be Chrome, Firefox. This would be two more environments which normally means 2 more Jenkins jobs. With this feature request, a filtered view would reduce Jenkins jobs and streamline reporting across all jobs where the build=XYZ.

Fewer Jenkins jobs is easier to manage and reporting is improved with parameter filtering.

Thanks,

Jim