php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #77356 ITS: Prevent marking tickets as duplicates without specifying original report
Submitted: 2018-12-27 04:53 UTC Modified: 2022-01-23 01:24 UTC
From: chealer at gmail dot com Assigned: cmb (profile)
Status: Wont fix Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: chealer at gmail dot com
New email:
PHP Version: OS:

 

 [2018-12-27 04:53 UTC] chealer at gmail dot com 
Description:
------------
I noticed a few tickets marked as duplicates without any indication of which tickets they would duplicate. For instance, the following 2 tickets have their Status field set to Duplicate, but the Related reports tab is empty:
https://bugs.php.net/bug.php?id=60024
https://bugs.php.net/bug.php?id=62132

As this is the result of changes by 2 developers, it looks like this is not exceptional, and would deserve a change in the system so developers cannot mark a ticket as duplicate when failing to specify a related ticket tracking the same issue.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2018-12-27 10:54 UTC] cmb@php.net 
Just to explain how that currently works: if a user refers to some
other ticket using “bug hash number”, the other ticket
automatically gets an entry “Related To: Bug hash number”.  These
entries can be filtered via the related reports “button”.  See,
for instance, <https://bugs.php.net/77347>, which has been closed
as duplicate of <https://bugs.php.net/77278>.  Only the latter has
a filterable related reports entry.  So, basically no duplicate is
presently supposed to show any related reports.

Also, there is a problem regarding comments which contain
inadvertant referrals to other tickets.  See, for instance,
<https://bugs.php.net/2307> which claims to be related to
<https://bugs.php.net/77349> which it is certainly not.

> […] and would deserve a change in the system so developers
> cannot mark a ticket as duplicate when failing to specify a
> related ticket tracking the same issue.

Hmm, that would require advanced AI, wouldn't it?

Anyhow, I suggest to move the discussion regarding possible
improvements of referrals and duplicates to the php-webmaster@
mailing list, since a bug tracker is unsuitable for brainstorming,
which is certainly necessary in this case.
 [2018-12-27 11:52 UTC] chealer at gmail dot com 
Ah, thank you for the explanation cmb, I see what you mean but I did not mean to suggest using any artificial intelligence, no. Sorry, I misunderstood how Related reports works.

I was rather suggesting a field to explicitly define the report with which a duplicate is redundant, as Bugzilla does:
https://www.tutorialspoint.com/bugzilla/bugzilla_duplicate.htm
https://bugzilla.mozilla.org/show_bug.cgi?id=548960

This field would appear when the Status field would be set to the value Duplicate. It would also allow other improvements to duplicate handling, like managing those who subscribe to a ticket automatically.
 [2022-01-20 17:06 UTC] cmb@php.net
-Status: Open +Status: Wont fix -Assigned To: +Assigned To: cmb
 [2022-01-20 17:06 UTC] cmb@php.net 
Given that bugsnet has been superseded by GH issues, it is
sufficiently safe to assume that this issue won't be fixed.
 [2022-01-23 00:45 UTC] chealer at gmail dot com 
Christoph, could you provide evidence that bugsnet has been superseded?
 [2022-01-23 00:58 UTC] cmb@php.net 
Looks like that's covered by
<https://wiki.php.net/rfc/github_issues>.
 [2022-01-23 01:24 UTC] chealer at gmail dot com 
Ah, thank you Christoph
And sorry for the question, although looking at that plan I guess it would be more correct to state that bugsnet *is being* superseded.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Apr 26 04:01:30 2024 UTC