Real Issue Tracker

Hmm... Strange. I think that when you assign an issue it creates a notification object (e.g. notification00001) inside the issue. So, (in /RSD) go to an issue where you have assigned someone and thus expect an email. Look at any of the notification objects in there and when you click on them and see all the properties you should be able to see a little checkbox at the bottom called "dispatched". What does it say? Is it checked or not?

What version are you running and if you use svn, what revision?

Hi, Thanks for the quick response.

Version information:
IssueTreacker version: 0.10.2

# Zope version: (Zope 2.11.1-final, python 2.4.4, win32)
# Python version: 2.4.4 (#0071, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)]
# System Platform: win32
# SOFTWARE_HOME: C:\Zope\2.11.1\Zope\lib\python
# INSTANCE_HOME: C:\Zope\Instance\2.11.1
# CLIENT_HOME: C:\Zope\Instance\2.11.1\var
# Process ID: 1444 (768)
# Running for: 4 days 12 hours 56 min 58 sec


I went into my working version /TEST and was able to locate the notification object and review the notification data...it made sense.

After that I went into my /RSD instance and there was no notification data on any of the issues, all of which should have had an assignment that was notified.

I'm assuming this means that notification is mis-configured. What would be my next step in identifying what I need to correct this?

Thanks Again for the help!

So, there is nothing wrong with the sending of the emails. It's just that notifications aren't created. Can you keep an eye on the event.log whilst you add assignments and see if shows any warnings or anything like that to explain why notification objects aren't created.

We might need to investigate what's going on with the checkbox that is next to assignment.

Thanks!

I restarted Zope and cleared the event.log file and the Z2.log file

After a restart I changed an assignment in the /RSD instance. I did this from a browser that was already open so that I could capture just that change.

I have attached a file called: event_RSD_instance.log
This is the event log file immediately after I changed an assignment in the RSD instance. there is really nothing in that file at all.

I have also attached a file that included the data in the Z2 log file at that time. It has more data, but I think is still only showing the GET/PUT requests that Zope receives.

Is there a physical event file somewhere on a per instance basis?

Is there a process to turn on detailed logging? If so I could log a successful change of assignment and a failed one.

Thanks Again
-Richard

Okay,

I did some more research on this. I think you have a logic bug in the notification process. I will try to detail two scenarios for you. One sends a notification, one does not.

Setup details:
User1: -> me, my email address
User2: -> a test employee, his email address
Issue: -> Issue #0001, exists and is assigned to User2

Scenario 1:
Using the details as listed above; I login as me (user 1) and change ownership to me for issue #0001. Result: no notification is sent

Scenario 2:
Using the details as listed above; User 2 logs in and changes ownership of Issue#1 to me (user1). Result: I get a notification email to user 1.
I can follow this up with me logging in after the email and changing the assignment back to User 2, and he will get an email too.

Working theory:
The end result is it appears as if the system is checking to see if the new assignee has the same email address of the active user and if so it does not send a notification email. The reason this bug is/was frustrating was that I had set up a number of test logins, but all of these had my email address for notification purposes. So every time I sent a test email it failed. To verify this I set up a second user with a g-mail address. I could then re-assign an issue back and forth several times and it would send a notification every time.

I hope this helps, and thanks for a great product. As soon as we go into production with our issue tracker we will be posting our success story to share with others.

-Richard

Well I don't think that is a bug then. I think it works like it should. It works on the premise that there's no point emailing yourself about something you've done. It's considered rare that people have users with the same email address. And if that is the case it's corner cases. Like people like you testing things.