Bug 132089 - rfe: add column "status" to the attachment list
rfe: add column "status" to the attachment list
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: David Lawrence
David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2004-09-08 14:24 EDT by Toni Willberg
Modified: 2007-04-18 13:11 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-08 14:55:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Toni Willberg 2004-09-08 14:24:11 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040803 Epiphany/1.2.7

Description of problem:
In the main view of a bug, the list of attachments is shown. The list
doesn't however tell if an attachment is marked as obsolete or a patch.

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

How reproducible:

Steps to Reproduce:
add an attachment, edit it afterwards and mark as obsolete

Additional info:

21:10 | <Tonyx> heh, just uploaded same image twice, and the list of
                attachments doesn't say which one is obsoleted
21:10 | <Tonyx>
21:11 | <Tonyx> it has columns "Attachment, Type, Created, Actions"
21:11 | <Tonyx> could have Status too
21:12 | <mitr> Interesting... Please file a bug in Product: bugzilla,
               dkl could fix it
Comment 1 David Lawrence 2004-09-08 14:55:25 EDT
Actually the answer is yes and no. If the attachment is not an image
file and just text or any other type, the link to it would be struck
out if the attachment is obsolete. With an image thumbnail this was
not possible and then also I failed to return to the issue. So now I
have added a status column as requested and did away with the strike
as well.


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