ADR New Search Criteria, Deployed = yes/no
I propose a new search criteria for ADR, to avoid multiple deployments for a single update. This is a pain to clean up afterwards.
Bryan Dam commented
I was thinking about this one a bit more since it got marked at noted today and I have a stretch goal of sorts. As described this would be a global Yes/No: the update is either deployed or not. If you have multiple ADRs this could be problematic. When more than one ADR selects a particular update then only the first ADR would win since it would be marked as deployed for subsequent ADRs.
The solution I think is to make the logic specific to the ADR deployments. Which is is to say "Is this update deployed to the collections targeted by this ADR". That's a lot more complex than just a global check but I think users will run into issues without it.
Allyn Jacobs commented
It seems like such a logical option choice, I am surprised that it hasn't been rolled out long ago..
Jay Gingras commented
Please add this feature
I may actually use ADR's once this is implemented! ;)
Eric Benda commented
The first time I looked at ADRs I looked for this filter first. Still stumped as to why its not there.
Meik Kurde commented
yes, please, do it
Bob Solimine commented
I agree with this 1000%! I have difficulty deploying updates without re-deploying older updates. I find I either re-deploy older updates extending the previous deadline or I miss new updates. I can't seem to get the filters right. Being able to simply filter for undeployed updates would make this so much simpler.
Yes please! Microsoft's 'best' practice which is widely used is to run ADRs monthly and create a new SUG. There's no way to filter out just the updates released since the last time the ADR ran. 'One month' simply subtracts from the date's month value causing it to miss updates. For example. Patch Tuesday was on the 14th in November 2017 so 'one month' would miss updates release between the previous Patch Tuesday (October 10) and October 14h.