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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0038697
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] B. User interfaceminorhave not tried2018-06-05 09:272022-02-01 08:05
ReporteralostaleView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix 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

0038697: in transactional filters incorrect range is displayed after modifying it

DescriptionIf a transactional window is opened in browser and afterwards the "Transaction Range" value in "Session Preferences" window is changed, when the window is opened again, the message for the transactional filter continues being the same as it was even the new range is properly applied.
Steps To Reproduce1. Open Sales Order window
   -> Check there is a message like:
     "This grid is filtered using a transactional filter (only draft & modified documents in the last 1 day(s))."
2. Close Sales Order window
3. Open Session Preferences window
4. Set 365 in Transaction Range
5. Open Sales Order window
   -> OK: booked orders modified up to 1 year ago are displayed
   -> ERROR: the message continues being the same (1 day)
6. Log out and log in again
7. Open Sales Order window
   -> ERROR: same as in step 5

This behavior continues until browser's cache is cleaned up.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0038516 closedcaristu Add a feature to allow to disable transactional filters in transactional windows easily without code changes 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2018-06-05 09:27 alostale New Issue
2018-06-05 09:27 alostale Assigned To => platform
2018-06-05 09:27 alostale Modules => Core
2018-06-05 09:27 alostale Triggers an Emergency Pack => No
2018-06-05 09:37 alostale Status new => acknowledged
2018-06-05 09:52 alostale Relationship added related to 0038516
2022-02-01 08:05 alostale Assigned To platform => Triage Platform Base


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker