Separate Filters for CI Jobs to reflect filter edits
Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.
It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.
Kris Goncalves
shared this idea
https://docs.gearset.com/en/articles/618760-custom-metadata-filters-in-compare-and-deploy-and-ci-jobs
-
Dafydd Johns commented
Critical for me - members of the team often have don't understand why certain things haven't been deployed. They can update the filter, but I'm only now understanding that CI jobs do not have a reference to the saved filter selected, it's just a point in time copy of the items selected.
Secondly, if someone modifies one CI job for a specific environment, and they don't remember to change the filter for an upper environment we then have no quick way of telling what the difference between two environment CI jobs is. Having a reference to a saved filter would allow us to centralise these filters and save time.
-
Jonathan Flatt commented
This is critical for me. I'd like to be able to set CI jobs to use the same locked-down filter and have changes to that filter reflect in the jobs using that filter. Ideally never managing more than 2-3 filters for the entire pipeline. Having to make the same updates in many jobs is tedious, error prone, and antithetical to the DevOps mindset.