Summary | Ingo deletes wrong rule |
Queue | Ingo |
Queue Version | 3.2.4 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | mrubinsk (at) horde (dot) org |
Requester | chris.hogan (at) 4xtra (dot) com |
Created | 07/24/2015 (3631 days ago) |
Due | |
Updated | 07/27/2015 (3628 days ago) |
Assigned | |
Resolved | 07/27/2015 (3628 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Michael Rubinsky
State ⇒ Resolved
commit 7574ff751e5c8840cd056edbffa1b322c30db6c3
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Mon Jul 27 13:25:35 2015 -0400
Bug: 14064andBug: 13643Fix reordering of rules.Rules were properly reordered in the backend, and the dom id of
the rules was updated, but the existing links that contained the
rule number was not. This should fix any remaining ordering issues.
Note that this does not need to be merged up to Git master since that
code was already heavily refactored to use rule uids instead of sort
position.
ingo/js/filters.js | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
http://github.com/horde/horde/commit/7574ff751e5c8840cd056edbffa1b322c30db6c3
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ Ingo deletes wrong rule
Type ⇒ Bug
State ⇒ Unconfirmed
redundant rule works perfectly. A second deleteion removes the rule
following the one selected.
The index is reset correctly if the rul list is regenerated by
re-entering the filters list or "return to filters list" from within
editing a rule