Bug 54651 - Displaying update date and calling it issue date
Displaying update date and calling it issue date
Status: CLOSED CURRENTRELEASE
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Devel
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Greg DeKoenigsberg
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-15 09:41 EDT by Jay Turner
Modified: 2015-01-07 18:52 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-15 11:48:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jay Turner 2001-10-15 09:41:14 EDT
Description of Problem:
On the new webqa pages, we have changed the errata displays to sort on the
update date for the errata, and we are displaying that date as well, but
the heading which is appearing is still calling it the "Issue Date"  Could
be confusing in that if the user clicks on the errata the next page will
show both the issue date and the update date.

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


How Reproducible:


Steps to Reproduce:
1. Log into https://rhn.webqa.redhat.com as rhn7_pager
2. Pull up /network/errata/errata_list.pxt
3. 

Actual Results:
Notice that the far-right column is labelled "Issue Date" and that the date
for RHBA-2001:121-05 shows as "12-OCT-01" but clicking on that errata shows
that the actual issue date is "4-OCT-01" and "12-OCT-01" is actually the
update date.

Expected Results:


Additional Information:
Comment 1 Chip Turner 2001-10-15 10:20:06 EDT
fixed in CVS
Comment 2 Jay Turner 2001-10-15 11:48:41 EDT
This looks pretty good on webdev.  Let's get it in the next webqa build.
Comment 3 Jay Turner 2001-11-15 21:19:11 EST
Closing this out as the change has propagated up.

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