allow for the ability to "lock" a metadata filter in for a CI job so that the CI job has any changes to filter.
Currently, the CI job takes the current metadata filters settings but does not used the updated settings. You have to re-add the filter back to the CI job. If checked on the CI job, the job would use the current filter's latest changes rather than the ones it was created with.
1
vote
OptimusCrime
shared this idea
You can now edit the CI job and choose to simply refresh the filter list so it grabs the latest changes to any of the filters and as a result will let your CI job use the most up-to-date settings.