Open Bug 12926 Opened 26 years ago Updated 7 months ago

When bug x mentioned in bug y, write this in bug x.

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: CodeMachine, Unassigned)

References

Details

(Keywords: bmo-ux, ux-efficiency, Whiteboard: [relations:other])

There's an existing capability in bugzilla to automatically hyperlinkify text in comments of the form bug #1 or bug 1. I propose that when a bug is mentioned in one report and hyperlinkified as such, the bug that is mentioned should have added something along the lines of: Comments in bug #2 mentioned this bug. Which would be hyperlinkified in a similar fashion to the duplicate message on the second bug. The rationale is that when you're mentioned by another bug, you may well be interested in that bug. If you mentioned a bug that was in the dependency lists, related lists (see bug #12286), has been, mentioned before, or bug currently as bug that is currently in a duplicate relationship, this "mentioning" message would not be added, since there is already an apparent relationship.
Summary: When bug x mentioned in bug y, write this is bug x. → When bug x mentioned in bug y, write this in bug x.
Status: NEW → ASSIGNED
Priority: P3 → P2
tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details, see my posting in netscape.public.mozilla.webtools, news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Status: ASSIGNED → NEW
My first thought on this is that this is potentially very hard to do correctly, cause I can think of a million ways where this would either have a performance impact or generate incorrect info. I'm thinking (and this pertains to an earlier bug as well), that we probably wanted to just maintain a "related" bug field that would solve a variety of related functional requests.
Status: NEW → ASSIGNED
I have never been totally comfortable with this request, for the reason that you might mention the bug, and then add it to deps or relations. An alternative might be to auto-add it to the related bugs field, and make sure you strip deps out of the related bugs field. Do the voters on this think it's worthwhile even if bug #12286 were implemented? I don't see a performance impact or incorrect info problem, but then I'm not a Perl/MySQL guru!
Well, I voted both for this bug and bug #12286. I think it would be worthwhile. I do think, however, that when bug x is mentioned in bug y, this shouldn't get mentioned in bug x if it has been mentioned before or if they have already been marked as having a relationship/dependancy to each other.
Adding default QA contact to all open Webtools/Bugzilla bugs lacking one. Sorry for the spam.
QA Contact: matty
Target Milestone: --- → Future
Perhaps we could maintain a "Mentioned" field. Then if it appears on deps, related or gets marked a dupe of this, it would disappear from mentioned.
*** Bug 82616 has been marked as a duplicate of this bug. ***
Moving to new Bugzilla product ...
Assignee: tara → myk
Status: ASSIGNED → NEW
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: other → unspecified
Whiteboard: [relations:other]
my vote to wontfix this bug. I much prefer bug 12286
Per discussion on IRC, I wontfix this bug. (23:41:58) LpSolit: you all agree to wontfix 12926? or that notifying dupes is annoying? (23:42:12) wicked: LpSolit: I agree with the wontfix (23:42:20) Colin: both (23:42:31) LpSolit: bkor: ? (23:43:08) bkor: LpSolit: wontfix
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Target Milestone: Future → ---
Bug 12286 is a valuable feature, but it doesn't make this one totally unuseful, since bug 12286's feature requires manual intervention, while this feature automatically gathers potentially related bugs. We should do both.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
QA Contact: mattyt-bugzilla → default-qa
Assignee: myk → create-and-change
Status: REOPENED → NEW
similar, but perhaps not quite the same, is the idea of a checkmark "copy comments to mentioned bugs" (bugs mentioned in the "additional comments" that is)
Priority: P2 → P3
Do you realize how easy it is to DoS Bugzilla with such a feature?? It's trivial to generate a script which mentions all bugs in a comment and submitting such a comment will spam all bugs... including those you are not allowed to see? I reiterate my wish to close it as wontfix.
as a default this definitely seems a bad idea, hence comment 12. but even so, this feature would not normally be of great help, and could even steer some people in the wrong direction given that some bug comments wildly speculate about relationships to other bugs. "related bugs" feature would be much more useful.
(In reply to comment #13) > Do you realize how easy it is to DoS Bugzilla with such a feature?? It's > trivial to generate a script which mentions all bugs in a comment and > submitting such a comment will spam all bugs... including those you are not > allowed to see? I reiterate my wish to close it as wontfix. Seems like a limit on the number of "bug mentions" would easily solve this.
This is a feature present in issue trackers like GitHub's, and I imagine many people find it to be quite useful. (I know I do.) Is there any chance of revisiting this?

I have put this RFE in my Bugzilla 7.0 Roadmap.

Assignee: create-and-change → kohei.yoshino
See Also: → 1352571
Assignee: kohei.yoshino → create-and-change

Possibly this could be more wisely addressed with a compiled and paginated "Bugs mentioned in this thread" box at the bottom of the page? rather than having new mentions show up inline?

I think Pulsebot is broken. That was supposed to be issue #12926 in GitHub not in Bugzilla.

Flags: needinfo?(aryx.bugmail)
You need to log in before you can comment on or make changes to this bug.