Closed
Bug 301080
Opened 19 years ago
Closed 5 years ago
[BUGZILLA] Ability to retreive info about attachments like we do for bugs
Categories
(Webtools Graveyard :: Mozbot, enhancement)
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: mkanat, Unassigned)
Details
Right now when I type "bug 123132" mozbot gets me some information about the bug. It would be nice if he could do the same thing for attachments, primarily to help out with the clarity of BugzillaMailHandler messages coming in about attachments. (That is, it says "canceled blah on attachment 1 [details] [diff] [review], requested review on attachment 2 [details] [diff] [review]" but we don't know what attachment 1 [details] [diff] [review] and 2 are.)
Comment 1•19 years ago
|
||
As far as I can tell, this would either: 1) Only work when a Bug Number was specified - so would be fine for "user @ example.com added attachment X to bug Y" and "user @ example.com requested X from Y for attachment Z on bug A" messages, but not for a user saying "attachment 212 [details] [diff] [review]" in general chat. or 2) Require a change to Bugzilla to provide an XML feed of attachment information which would work around these problems. as the only way I can currently see to get attachment information in an XML format is by using the output of "show_bug.cgi?ctype=xml", which of course requires a bug number.
Reporter | ||
Comment 2•19 years ago
|
||
Yeah, it would require a modification of Bugzilla itself, I was thinking.
Updated•18 years ago
|
QA Contact: kerz → mozbot
Comment 3•16 years ago
|
||
Cleaning up mozbot's buglist. I'm assuming you're not longer interested in fixing this (if its even possible). Feel free to take it back if i'm wrong. :-)
Assignee: mkanat → nobody
Reporter | ||
Comment 4•13 years ago
|
||
bugbot is fully capable of doing this now, BTW.
Mozbot/Firebot is in maintenance-only mode; no further changes are planned.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
Updated•5 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•