Summary | When assigning people responsible for a new queue, I select them from the dropdown and then when saved, my email is repeated once for each assignment. |
Queue | Whups |
Type | Bug |
State | Duplicate |
Priority | 1. Low |
Owners | |
Requester | eculp (at) encontacto (dot) net |
Created | 06/05/2008 (6241 days ago) |
Due | |
Updated | 07/30/2008 (6186 days ago) |
Assigned | |
Resolved | 06/05/2008 (6241 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
I finally figured out that it is using the current user ID for all
assigned emails. I logged in as cmorando@casasponti.net aftering
giving admin permisions to this user. I then assigned the "cambio"
queue to aodria@casasponti.net and got the following messege from whups:
Se ha añadido a aodria@casasponti.net <cmorando@casasponti.net> a los
encargados de "cambio"
....................................
^^^^^^^^^^^^^^^^^^
Notifications will obviously be sent to cmorando@casasponti.net
rather that aodria@casasponti.net as desired.
Now to find where the userid or mail address is being added dynamically.
The database is fine.
3 aodria@casasponti.net
It has to be configuration.
assigned emails as en:
Se ha añadido a aodria@casasponti.net <cmorando@casasponti.net> a los
encargados de "cambio"
where I logged in as cmorando@casasponti.net and assigned the
"cambios" queue to aodria@casasponti.net. The email will obviously be
sent to cmorando@casasponti.net.
Now I have to figure out where that is being assigned.
not include all the history but the most recent discovery.
I am still suffering with this and after starting with all new -
database, programs, configuration - it was ok for a bit but is doing
it again. I'm convenced that the problem isn' t whups but somewhere
else. I am now thinking it has to do with turba and my ldap
configuration. For example, when I look at a ticket that has been
assigned to three people, it shows up as:
Owners Edwin L (dot) Culp <eculp (at) casasponti (dot) net>,
rrodriguez (at) casasponti (dot) net <eculp (at) casasponti (dot)
net>, smartinez (at) casasponti (dot) net <eculp (at) casasponti (dot)
net>
With my email enclosed with <> after each assignee but the database
for the same ticket shows:
2 user:eculp@casasponti.net
2 user:rrodriguez@casasponti.net
2 user:smartinez@casasponti.net
which is correct.
after making a comment the email is sent as per the following maillog:
-------------------------- first ------------------------------------
Jul 30 06:26:15 casasponti courierd:
started,id=00130C6A.48904FD7.0000704C,from=<webmaster@casasponti.net>,module=local,host=eculp@casasponti.net!!80!80!/h
ome/virtual/casasponti.net/eculp!!20000000S,addr=<eculp@casasponti.net>
Jul 30 06:26:15 casasponti courierd: Waiting. shutdown time=none,
wakeup time=Wed Jul 30 06:42:30 2008, queuedelivering=3, inprogress=1
Jul 30 06:26:15 casasponti courierlocal:
id=00130C6A.48904FD7.0000704C,from=<webmaster@casasponti.net>,addr=<eculp@casasponti.net>,size=2456,success:
Messa
ge delivered.
------------------------------ second ----------------------------
Jul 30 06:26:15 casasponti courierd: completed,id=00130C6A.48904FD7.0000704C
Jul 30 06:26:15 casasponti courierd: Waiting. shutdown time=Wed Jul
30 07:15:45 2008, wakeup time=Wed Jul 30 06:42:30 2008,
queuedelivering=2, inprogress=
Jul 30 06:26:15 casasponti courierd:
newmsg,id=00130CEB.48904FD7.00007054: dns; localhost (localhost
[127.0.0.1])
Jul 30 06:26:15 casasponti courierd:
started,id=00130CEB.48904FD7.00007054,from=<webmaster@casasponti.net>,module=local,host=eculp@casasponti.net!!80!80!/h
ome/virtual/casasponti.net/eculp!!20000000S,addr=<eculp@casasponti.net>
Jul 30 06:26:15 casasponti courierd: Waiting. shutdown time=none,
wakeup time=Wed Jul 30 06:42:30 2008, queuedelivering=3, inprogress=1
Jul 30 06:26:15 casasponti courierlocal:
id=00130CEB.48904FD7.00007054,from=<webmaster@casasponti.net>,addr=<eculp@casasponti.net>,size=2448,success:
Messa
ge delivered.
---------------------------- third ---------------------------
Jul 30 06:26:15 casasponti courierd:
started,id=00130CF1.48904FD7.0000705C,from=<webmaster@casasponti.net>,module=local,host=eculp@casasponti.net!!80!80!/h
ome/virtual/casasponti.net/eculp!!20000000S,addr=<eculp@casasponti.net>
Jul 30 06:26:15 casasponti courierd: Waiting. shutdown time=none,
wakeup time=Wed Jul 30 06:42:30 2008, queuedelivering=3, inprogress=1
Jul 30 06:26:15 casasponti courierlocal:
id=00130CF1.48904FD7.0000705C,from=<webmaster@casasponti.net>,addr=<eculp@casasponti.net>,size=2460,success:
Messa
I just noticed that the owners cannot be deleteded form the queue even
though the option exists. That could be a bug. I had to delete them
manually from the whups_ticket_owners table.
I added three users and DIDNOT include myself and got the following results:
aodria@casasponti.net <eculp@casasponti.net>,
rrodriguez@casasponti.net <eculp@casasponti.net>,
smartinez@casasponti.net <eculp@casasponti.net> added to those
responsible for "PontiNet"
That will again send all the emails to me. This has to be a
configuration error but I still have no idea where.
IMO, the above pretty well rules out turba.
I'm not expecting help just hope that something that I have shown here
will turn on a light.
Thanks.
ever able to reproduce. If you can help someone reproduce it, great,
Sorry, I'm not sure if I should close this one. In the meantime, to
try and narrow down the problem, I have erased the installed framework
in pear and in the cvs co, all the whups tables, and the whups co and
have done new checkouts of all, reconfigured whups, and reinstalled
the new framework just to eliminate anything stale. The problem still
persists. I am now going to do the same with horde and turba,
especially hooks to try and find any old configurations that are
causing the problem. I am going to use this ticket to keep a registry
of what I have done and for any suggestions that anyone might have.
Testing after the above display's the same as the screenshot, but I
happened to du a mysqldump and found that the database is correct:
LOCK TABLES `whups_queues_users` WRITE;
/*!40000 ALTER TABLE `whups_queues_users` DISABLE KEYS */;
INSERT INTO `whups_queues_users` VALUES \
(1,'aodria@casasponti.net'),(1,'eculp@casasponti.net'),(1,'rrodriguez@casasponti.net');
/*!40000 ALTER TABLE `whups_queues_users` ENABLE KEYS */;
UNLOCK TABLES;
The display still shows eculp@casasponti.net three times. Little by
little, I plan to erase module by module and build all new
configurations until I find the problem.
State ⇒ Duplicate
ever able to reproduce. If you can help someone reproduce it, great,
but please don't open duplicate tickets.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ When assigning people responsible for a new queue, I select them from the dropdown and then when saved, my email is repeated once for each assignment.
Queue ⇒ Whups
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
the dropdown and then when saved, my email is repeated once for each
assignment. A screen shot is at
http://encontacto.net/SHARE/TicketAssignment.png
I use ldap for user and auth but all is well on those fronts. I had
this before but lost my patience with it and just quit using whups.
This time I'm going to take it to the end even though I have a hard
time believing it myself.
Thanks,