Anonymous | Login | 2024-08-24 20:52 EDT | ![]() |
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 | |||
0001609 | PacketFence | web admin | public | 2012-11-18 14:52 | 2015-02-18 10:59 | |||
Reporter | muhlig | |||||||
Assigned To | ||||||||
Priority | normal | Severity | feature | Reproducibility | always | |||
Status | closed | Resolution | open | |||||
Platform | OS | OS Version | ||||||
Product Version | 3.6.0 | |||||||
Target Version | Fixed in Version | |||||||
Summary | 0001609: Alerting subject prefix should be more configurable | |||||||
Description | ALERTING.SUBJECTPREFIX - You say: "Default: PF Alert: Subject prefix for email notifications of rogue DHCP servers, violations with an action of "email", or any other PacketFence-related message.". I'd like to have different prefixes for different notifications, for instance: "PF Alert", "PF Violation", "PF General", to make possible mail sorting to different mailboxes. Thank you. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
![]() |
|
(0003923) lmunro (administrator) 2015-02-18 10:59 |
Obsolete bug tracker entries. PF 4 introduced changes that either make these irrelevant or impossible to reproduce. New issues are moving to github issues. |
![]() |
|||
Date Modified | Username | Field | Change |
2012-11-18 14:52 | muhlig | New Issue | |
2012-11-19 10:20 | francis | Summary | Alerting subjest prefix should be more configurable => Alerting subject prefix should be more configurable |
2015-02-18 10:59 | lmunro | Note Added: 0003923 | |
2015-02-18 10:59 | lmunro | Status | new => closed |
Copyright © 2000 - 2012 MantisBT Group |