PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001474PacketFenceweb adminpublic2012-06-21 10:412012-09-06 10:57
Reporterfgaudreault 
Assigned Tofgaudreault 
PrioritylowSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versiondevel 
Target Version3.5.1Fixed in Version3.5.1 
Summary0001474: Release Date should be added automatically when closing a violation if nothing is specified in the field
DescriptionOn the web admin, when closing a violation, it should automatically put now() as the release_date. Idem when the user close it from the portal.
TagsNo tags attached.
fixed in git revisionfc8320925c43602e6614d341c574a533934d169c
fixed in mtn revision
Attached Files

- Relationships
related to 0001475resolvedfgaudreault Refactor the Bandwidth accounting violation process 

-  Notes
(0002820)
fgaudreault (viewer)
2012-06-22 17:50
edited on: 2012-06-22 17:53

Branched in feature/acct_violations

I went even further:
- Added a fast close/open button:
 * Closing using that button will put NOW as the release_date
 * Opening using that button will remove the release_date (and open the violation). We can see if we want to put the new release_date then (if we open a violation with a window).

- Added a "window" concept to the violations (just like unregdate)
 * You can define a period of time you want the violation to be active
 * Past that time, the violation will be closed by pfmon automatically
 * Supports the normalized format + "dynamic" keyword (see below). "0" is considered forever.

TO DO:
- Support the dynamic keyword (for accounting violations). The core will calculate the appropriate window.
 * Exemple: I have an accounting violation of 20G/month, I want to put the release date at the end of the month if you trigger the limit after say 3days.

(0002845)
fgaudreault (viewer)
2012-07-19 11:08

Ready in acct_violations. Missing the doc updates tho.
(0002869)
fgaudreault (viewer)
2012-08-03 17:10

All fixed in devel!
(0003027)
obilodeau (reporter)
2012-09-06 10:57

fix released in 3.5.1 yesterday

- Issue History
Date Modified Username Field Change
2012-06-21 10:41 fgaudreault New Issue
2012-06-21 10:46 fgaudreault Relationship added related to 0001475
2012-06-22 17:50 fgaudreault Note Added: 0002820
2012-06-22 17:51 fgaudreault Note Edited: 0002820
2012-06-22 17:52 fgaudreault Note Edited: 0002820
2012-06-22 17:53 fgaudreault Note Edited: 0002820
2012-07-19 11:08 fgaudreault Note Added: 0002845
2012-08-03 17:10 fgaudreault git revision => fc8320925c43602e6614d341c574a533934d169c
2012-08-03 17:10 fgaudreault Note Added: 0002869
2012-08-03 17:10 fgaudreault Status new => resolved
2012-08-03 17:10 fgaudreault Resolution open => fixed
2012-08-03 17:10 fgaudreault Assigned To => fgaudreault
2012-08-03 17:10 fgaudreault Fixed in Version => +1
2012-09-06 10:56 obilodeau Target Version => 3.5.1
2012-09-06 10:56 obilodeau Fixed in Version +1 => 3.5.1
2012-09-06 10:57 obilodeau Note Added: 0003027
2012-09-06 10:57 obilodeau Status resolved => closed


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker