Bug 82974 - RFE: Display ticket ID in all ticket views
Summary: RFE: Display ticket ID in all ticket views
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site
Version: RHN Devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Robin Norwood
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 79937
TreeView+ depends on / blocked
 
Reported: 2003-01-29 04:53 UTC by Greg DeKoenigsberg
Modified: 2007-04-18 16:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-18 19:11:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Greg DeKoenigsberg 2003-01-29 04:53:31 UTC
There's no way for support techs to reference tickets externally, because we
never display the ticket ID in a useful way.

We need to display the ticket ID in ticket list views and detail views.

Also, we should probably have a "go to ticket by number" form or something.

Comment 1 Robin Norwood 2003-01-30 21:34:14 UTC
This is rolled into payloaders.

Comment 2 Josef Komenda 2003-01-30 22:43:01 UTC
Please implement.

Comment 3 Robin Norwood 2003-01-31 02:37:58 UTC
This feature is in, on the following pages:

/internal/feedback/feedback_details.pxt

/internal/feedback/feedback_reply.pxt



Comment 4 Josef Komenda 2003-01-31 15:54:02 UTC
The request was for this to be in details, lists, and add a search. I only see
it in details. It seems kind of late to add even more stuff, so I'll defer the
other parts until the point release. 

Comment 5 Robin Norwood 2003-02-14 18:34:18 UTC
Fixed in head - aligning with next HEAD push bug.

Comment 6 Josef Komenda 2003-02-17 19:18:03 UTC
Oh my goodness, what in Hera's name is this?  border-left: 1px solid black? 
Surely there must be something, anything better than this... Over to rnorwood.
Please see garrett for advice on this. 


Comment 7 Josef Komenda 2003-02-18 19:11:53 UTC
Ugly, but internal, closing.


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