Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0026772
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 01. General setupmajoralways2014-06-03 16:302014-07-04 07:55
ReportermaiteView Statuspublic 
Assigned Tojonalegriaesarte 
PriorityurgentResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0026772: Should implement a feature to execute again alerts defined as type 'E' (external)

DescriptionThis kind of alert definition improve performance but have the handicap that can not be executed again by scheduling "Alert background" process. Also, at the moment, is not possible to manually set an alert as "Solved" so some alternative should be implemented to allow user to execute alert query again and verify that records have been solved.
Steps To Reproduce1. Ensure that alert "WrongMatchInvAccounting" finds any erroneous record
2. Correct related accounting
3. Execute query directly against database to verify that no records is found
4. Realize that is not possible to execute alert again to records remain in "Alert management"
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to feature request 0026203 newAugustoMauch Add the possibility to specify the alerts to be executed on each background scheduling 
related to defect 00255113.0PR14Q2 closedAtulOpenbravo Performance problems with 2 alertrule created by ModuleScript: Issue21640WrongMatchInvAccounting 
related to defect 00262423.0PR14Q3 closedAtulOpenbravo Orders could be reactivated although they have a related payment if it is not paid 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2014-06-03 16:30 maite New Issue
2014-06-03 16:30 maite Assigned To => dmiguelez
2014-06-03 16:30 maite Modules => Core
2014-06-03 16:30 maite Triggers an Emergency Pack => No
2014-06-03 16:30 maite Relationship added related to 0026203
2014-06-03 16:30 maite Relationship added related to 0025511
2014-06-03 16:30 maite Relationship added related to 0026242
2014-07-04 07:55 dmiguelez Assigned To dmiguelez => jonalegriaesarte

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker