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 454503 - Rewrite or remove "New Events" group view column code
Summary: Rewrite or remove "New Events" group view column code
Status: NEW
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: User Interface
Version: 4.6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Issue-Tracker Bug Watch List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-08 20:56 UTC by Gary Case
Modified: 2008-07-08 22:56 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Gary Case 2008-07-08 20:56:59 UTC
Description of problem:
Group views can be modified to display a column called New Events. This column
shows the number of updates a ticket has received since the last time the
current user viewed it. The current implementation of this code is too
computationally intensive, resulting in timeouts/proxy errors if the column is
selected for display.

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

How reproducible:
Every time.

Steps to Reproduce:
1. Log in to Issue Tracker
2. Alter a group view to include the New Events column.
3. Attempt to save the view
Actual results:
Timeout or proxy server error.

Expected results:
Group view with New Events column present.

Additional info:

Comment 1 Gary Case 2008-07-08 22:56:58 UTC
I also just discovered that public and private entries are counted regardless of
account type (internal or external account). This leads to new ticket entries
that cannot be cleared out of the New column by external accounts. If we decide
to fix this column, we should rewrite the code to not count private updates when
a non-RH account is viewing tickets.

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