Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 456318 - "Filter to Geography" filter serves no purpose; please remove
Summary: "Filter to Geography" filter serves no purpose; please remove
Keywords:
Status: NEW
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: User Interface
Version: 4.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Issue-Tracker Bug Watch List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-22 19:36 UTC by Gary Case
Modified: 2008-07-22 19:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Gary Case 2008-07-22 19:36:20 UTC
Description of problem:

I believe the "Filter to Geography" filter can be removed, because it can only
show you all tickets or no tickets in a group. It can't do any useful filtering.
Let me explain:

Filter to Geography - Base Groups
---------------------------------
Let's say I have a ticket in group "NA Intel" which has a GEO of NA. If I go to
the NA Intel group view and set the Filter to Geography filter to "None" or
"NA", I'll see every ticket in the group because the NA Intel group has a base
group of NA. If I set the filter to APAC or EMEA, I'll see no tickets.

Filter to Geography - Escalation Groups
---------------------------------------
I escalate a ticket from my "NA Intel" group into an escalation group called
"EMEA Escalations", which has a GEO of EMEA. If I go to the EMEA Escalations
group view and set the Filter to Geography filter to "None" or "EMEA", I'll see
every ticket in the group, regardless of base group, because the EMEA
Escalations group has a base group of EMEA. If I set the filter to NA or APAC,
I'll see no tickets, as the EMEA Escalations group has the EMEA GEO.



The Filter to Originating Geography filter looks at the GEO of a ticket's base
group to determine whether a ticket should be displayed or hidden. It will still
be a 0% or 100% filter for base groups, but you'll see something different (and
useful) in escalation groups:

Filter to Originating Geography - Base Groups
---------------------------------------------
Once again I have a ticket in group "NA Intel" which has a GEO of NA. If I
activate the Filter to Originating Geography filter on the NA Intel group view
and set it to "None" or "NA", I will see all tickets in the group. If it is set
to APAC or EMEA, no tickets will be displayed. It's the same 0% or 100% behavior
we see with the "Filter to Geography" filter on base groups.

Filter to Originating Geography - Escalation Groups
---------------------------------------------------
Here's where things are different. If I escalate my "NA Intel" ticket into "EMEA
Escalations", The Filter to Originating Geography filter ignores the EMEA GEO of
the escalation group and instead looks at the tickets' base groups. If I set the
filter to "None", I see all tickets in the escalation group. If I set the filter
to "NA", I see all tickets in the group that are in base groups with the NA GEO.
If I set it to "EMEA", I'll see all tickets in EMEA base groups. The same holds
true when I set the filter to APAC.

Unless I'm completely wrong in my interpretation of how these different filters
work, I believe we could eliminate the "Filter to Geography" filter entirely, as
all of its useful functionality is contained within "Filter to Originating
Geography". In fact, we may want to consider adding text like (escalation groups
only) below the Filter to Originating Geography filter to show people that it's
only useful for escalation groups.



Version-Release number of selected component (if applicable):
4.6

How reproducible:
Always

Steps to Reproduce:
See first section.
  
Actual results:
See first section.

Expected results:
See first section.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.