
| Key: |
CHD-1931
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Assignee: |
Unassigned
|
| Reporter: |
Joe Geck
|
| Votes: |
0
|
| Watchers: |
0
|
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
chd-1931.diff (2 kb)
|
|
Environment:
|
5.0.0-pl1 (Build 2010052401)
|
|
| Value: |
1 - Must Have
|
| Marquee: |
Mail
|
Summary:
After getting this report, I tested every combination I could think of. It turns out it's this one specific case with Send Mail (or quick compose from Address Book).
Steps:
1) Enable a CLOSED ticket auto-response inside Dispatch.
2) Compose a new message from Send Mail or the Address Book, make sure you select "closed" status in the 'Next' section prior to sending off.
3) View the message and observe the ticket conversation.
Result:
You should see a 'queued' message representing the close ticket auto, with "To: (requesters)" and no subject. Because it's invalid, it will sit in the 'Mail Queue' until corrected.
|
|
Comment by Joe Geck [01/Jun/10 02:39 PM]
Comment by Joe Geck [02/Jun/10 06:40 AM]
Fixed for 5.0.0-pl1
Comment by Joe Geck [09/Jun/10 04:49 PM]
Verified fixed in 5.0.0-pl1 (Build 2010060701). Closing out, threads updated.
|
|