Proximity Adjustment rules can be used too broadly

Bug #1269906 reported by Mike Rylander
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Medium
Unassigned
2.4
Undecided
Unassigned
2.5
Undecided
Unassigned

Bug Description

The canonical use case for proximity adjustment is to use it broadly to effect the local proximity of items within a particular area, in a like manner, across many parts of the org tree. However, in cases where it is lightly used, or used with non-overlapping criteria columns, there are cases where the adjustment will spread beyond its intended range of influence.

The changes here create a much stricter and correct test for rule matching, which will end in the correct choice of rules in all cases.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/prox-adjust-fix

Changed in evergreen:
milestone: none → 2.6.0-alpha1
Revision history for this message
Lebbeous Fogle-Weekley (lebbeous) wrote :

This branch adds my signoff to Mike's two commits and a test in the third, which is good not only for its own sake but because it adds a more concrete expression of what's right behavior (and what proximity adjustment was formerly getting wrong).

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/senator/prox-adjust-fix

Revision history for this message
Mike Rylander (mrylander) wrote :

Pushed to the appropriate branches. Thanks for the test and signoff, Lebbeous!

Changed in evergreen:
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers