Anonymous | Login | Signup for a new account | 2021-01-21 04:36 GMT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0001336 | SiT! | outbound email | public | 2010-06-03 15:45 | 2010-06-05 11:04 | ||||||||
Reporter | ivan | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | feature | Reproducibility | N/A | ||||||||
Status | acknowledged | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001336: Add an email header to say which email template / trigger was used | ||||||||||||
Description | Add an email header to say which email template / trigger was used. This will help with debugging mail problems. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
![]() |
|
ivan (administrator) 2010-06-03 17:34 |
Would be good if every email had a header to say the source, including password reset emails and emails sent from incidents. |
paulh (administrator) 2010-06-05 11:04 |
Agree this could be useful, not sure about it being enabled all the time though, perhaps only when debug is on? Or perhaps we need another config option as some people may now want their end users being able to find out why the trigger fired or what the template was called (perhaps the name of the template isn't good publicly facing?) |
![]() |
|||
Date Modified | Username | Field | Change |
2010-06-03 15:45 | ivan | New Issue | |
2010-06-03 17:34 | ivan | Note Added: 0003229 | |
2010-06-05 11:04 | paulh | Note Added: 0003231 | |
2010-06-05 11:04 | paulh | Assigned To | => administrator |
2010-06-05 11:04 | paulh | Status | new => acknowledged |
2010-06-05 11:04 | paulh | Assigned To | administrator => |
Copyright © 2000 - 2021 MantisBT Team |