Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010510Openbravo ERPA. Platformpublic2009-09-08 10:032011-04-01 18:44
Reporterpjuvara 
Assigned Toiperdomo 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version2.50MP1 
Target VersionFixed in Version3.0RC6 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0010510: Alert window does not preseve status when navigating back
DescriptionIn the alert window, you can restrict the displayed records to a subset using the Alert Rule filter.
However, when you then review a particular alert and drill down into one of the records and navigate back, the filter is not honored anymore and all active alerts are shown.

This behavior is very annoying as it makes the review of alerts a lot more time consuming than it should be.

This significantly reduces the value of the alert functionality.
Steps To Reproduce1) In an instance with many alerts (100+) generated by more than one alert rule
2) In General Setup || Application || Alert Management filter the set of displayed alert searching by alert rule
3) Navigate to the record details of an alert
4) Navigate back
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0016481 closed gorkaion Alert window does not preseve status when navigating back 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-09-08 10:03pjuvaraNew Issue
2009-09-08 10:03pjuvaraAssigned To => rafaroda
2009-09-08 10:03pjuvaraOBNetwork customer => No
2009-09-18 07:19rafarodaNote Added: 0020164
2009-09-18 07:19rafarodaStatusnew => feedback
2009-09-18 07:19rafarodaversion => 2.50MP1
2009-09-18 07:19rafarodaTarget Version2.50MP1 =>
2009-09-18 14:52pjuvaraNote Added: 0020214
2009-09-18 14:52pjuvaraStatusfeedback => new
2009-09-18 15:13rafarodaNote Added: 0020216
2009-09-18 15:13rafarodaPrioritynormal => high
2009-09-18 15:13rafarodaStatusnew => scheduled
2009-09-18 15:13rafarodaProposed Solution updated
2010-02-11 18:05rafarodaAssigned Torafaroda => adrianromero
2011-03-17 19:45dmitry_mezentsevAssigned Toadrianromero => gorkaion
2011-03-17 19:47dmitry_mezentsevNote Added: 0035020
2011-03-25 11:36gorkaionIssue cloned0016481
2011-03-25 11:36gorkaionRelationship addedrelated to 0016481
2011-03-25 11:38gorkaionNote Added: 0035241
2011-03-25 11:38gorkaionAssigned Togorkaion => iperdomo
2011-03-25 11:38gorkaionfix_in_branch => 2.50
2011-03-25 11:38gorkaionTypedefect => backport
2011-04-01 18:44dmitry_mezentsevNote Added: 0035484
2011-04-01 18:44dmitry_mezentsevStatusscheduled => closed
2011-04-01 18:44dmitry_mezentsevResolutionopen => fixed
2011-04-01 18:44dmitry_mezentsevFixed in Version => 3.0RC6

Notes
(0020164)
rafaroda   
2009-09-18 07:19   
Paolo,

We have not been able to reproduce this issue.

Please try to reproduce it in the last pi version and give more details.

Thanks,.
(0020214)
pjuvara   
2009-09-18 14:52   
I cannot test in PI but it does not work in 2.50 MP5, the latest production version. Please verify there.
(0020216)
rafaroda   
2009-09-18 15:13   
Yes, it does reproduce. I did not realized that you were talking about the Alert Management window, not the Alert one.
(0035020)
dmitry_mezentsev   
2011-03-17 19:47   
We are redesigning Aler Management window now. In general in this design in 3.0 issue won´t exist any longer because of tab navigation.

Anyway assigning now issue to Gorka to close it once window is finished.
(0035241)
gorkaion   
2011-03-25 11:38   
Changed to backport, issue on 3.0 has been closed due to the redesign of the window.
(0035484)
dmitry_mezentsev   
2011-04-01 18:44   
I think it does not make sense to keep this issue in 2.50 because we are not going to fix it there.