Bug 1179620

Summary: IE 11: Drill Down using selectable table cells / canceling filter properties not working
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jan Hrcek <jhrcek>
Component: BAMAssignee: Roger Martínez <romartin>
Status: CLOSED WORKSFORME QA Contact: Jan Hrcek <jhrcek>
Severity: high Docs Contact:
Priority: medium    
Version: unspecifiedCC: jhrcek, kverlaen, mbaluch, rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-21 07:14:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
About IE screen
none
IE version - QA none

Description Jan Hrcek 2015-01-07 08:42:05 UTC
Description of problem:
When you drill down by clicking Table KPI cells, only the first filtered property is added to the dashboard filter. When trying to add more properties to the filter by clicking table cells, nothing happens. Also it is impossible to delete filtered properties from the filter.


Version-Release number of selected component (if applicable):
BPM Suite 6.1. ER3 with Internet Explorer 11

How reproducible:
Always

Steps to Reproduce:
1. Go to Showcase > Sales report
2. Try filtering data by clicking multiple table cells and then canceling the filtered properties in dashboard filter

Actual results:
Only the first filtering click works, after that it's impossible to continue filtering by additional properties, nor to cancel filtered properties.

Expected results:
Each click on selectable table cell should restrict data and add filtered property to the dasbhoard filter. Also it should be possible to delete filtered properties from dashboard filter.

Additional info:
This works in firefox and chrome, but is broken in Internet Explorer (so far tested with IE 11, I will add more info about status on IE 10 & 9 asap)

Comment 1 Jan Hrcek 2015-01-08 08:22:27 UTC
I just checked that this issue is NOT present in IE 9 and 10, so it is IE11-ONLY issue.

I strongly suspect it might have something to do with the fix to bug #1127150 (see its Doc Text) which was introduced with this build.

Comment 2 Roger Martínez 2015-01-08 17:40:00 UTC
(In reply to Jan Hrcek from comment #1)
> I just checked that this issue is NOT present in IE 9 and 10, so it is
> IE11-ONLY issue.
> 
> I strongly suspect it might have something to do with the fix to bug
> #1127150 (see its Doc Text) which was introduced with this build.

Hi Jan,

Please can you specify the concrete version of IE-11 you are using? 

I cannot reproduce it neither in master and 6.2.x branches using IE-11.0.960017280. 

As emulation setting values (F12) I have the default ones configured, which are:
- document mode: edge (default)
- explorer profile: desktop
- user agent: default

Do you have more clues about the issue? Thanks!

Comment 3 Roger Martínez 2015-01-08 17:40:49 UTC
Created attachment 977864 [details]
About IE screen

Comment 4 Jan Hrcek 2015-01-09 05:54:37 UTC
Hi Roger,
this is strange. I just double checked on the same machine and I too cannot reproduce the problem anymore. My IE settings are the same as yours, version 11.0.9600.17351, I'm attaching screenshot. I have an automated test for this now, so let's keep this open for a while and see whether it will happen again. If it does, I'll try to investigate it in more detail.

Comment 5 Jan Hrcek 2015-01-09 05:55:16 UTC
Created attachment 978035 [details]
IE version - QA

Comment 6 Roger Martínez 2015-01-09 11:01:00 UTC
(In reply to Jan Hrcek from comment #4)
> Hi Roger,
> this is strange. I just double checked on the same machine and I too cannot
> reproduce the problem anymore. My IE settings are the same as yours, version
> 11.0.9600.17351, I'm attaching screenshot. I have an automated test for this
> now, so let's keep this open for a while and see whether it will happen
> again. If it does, I'll try to investigate it in more detail.

Hi Jan,

Ok! No problem. Let's keep it open for a while and let's see if it happens again.

Thanks!

Comment 8 Jan Hrcek 2015-01-21 07:14:46 UTC
I'm not able to reproduce it anymore. Both manual and automated tests are passing, so closing this as NOTABUG.