[Tickets #2617] RESOLVED: Filtering on "Sender" does not use "From"

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2617
-----------------------------------------------------------------------
 Ticket             | 2617
 Updated By         | robert at defore.st
 Summary            | Filtering on "Sender" does not use "From"
 Queue              | Ingo
 Version            | HEAD
 State              | Rejected
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


robert at defore.st (2005-12-01 22:36) wrote:

I don't have the resources to convert my suggestions into patches, and I
didn't think any comments I could add would clarify or otherwise help.

My intent in opening this ticket was to help the Horde project.  I found an
aspect of the software which is confusing.  The problem I described is real.
 Nothing about what I reported is inaccurate, and both my wife and I were
confused by the program.  I don't see why this ticket should be closed. 
There's no need to fix it right away, but until the problem goes away, why
not track it as a problem?  Maybe someone new to the project will look
through the tickets looking for easy problems to solve, like changing the
contents of menus to be less confusing.  Or maybe someone more experienced
will look for problems whose preferred sollution is hard with the current
framework, so they can find ways the framework could be improved to make
those solutions easier.

There's no reason why you should feel compelled to invest any effort in the
problem, but don't reject a ticket just because you don't want to do it. 
Reject it because it's not reproducable.  Reject it because the user is
insane, which I'll admit is a possibility. If it's insanity, be more clear
in that respect.  Don't reject it because the user hasn't fix the problem
themselves yet.

My problem is 'solved' for me in that I have a work-around (use the right
field name), but the root problem itself is still there.  There's no cost to
leaving a ticket open if the ticket is describing a real problem regardless
of whether it's UI, documentation or a 'bug'.  

Anyway, leave the ticket 'rejected' if you want, but you're wasting
information if you do.  Noone is going to look through rejected tickets
looking for real problems.  This problem will only get fixed if someone
knows about it and wants to fix it, or if some unrelated change makes the
problem moot.  I suggest you leave the ticket open, and at lowest priority,
until someone determines that the problem is not real or is fixed.

And if my input is not considered helpful, then I appologize.  I have
nothing but the highest hopes for the Horde project, its modules and its
developers.