Setting the status of this back to New due to the release of the refactored hold targeter in 2.12 (bug 1596595). Can anyone confirm this is still a problem with the new targeter in place?
Setting the status of this back to New due to the release of the refactored hold targeter in 2.12 (bug 1596595). Can anyone confirm this is still a problem with the new targeter in place?