Edit report at https://bugs.php.net/bug.php?id=77356&edit=1

 ID:                 77356
 Updated by:         c...@php.net
 Reported by:        chealer at gmail dot com
 Summary:            ITS: Prevent marking tickets as duplicates without
                     specifying original report
 Status:             Wont fix
 Type:               Feature/Change Request
 Package:            Website problem
 PHP Version:        Irrelevant
 Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

Looks like that's covered by
<https://wiki.php.net/rfc/github_issues>.


Previous Comments:
------------------------------------------------------------------------
[2022-01-23 00:45:18] chealer at gmail dot com

Christoph, could you provide evidence that bugsnet has been superseded?

------------------------------------------------------------------------
[2022-01-20 17:06:32] c...@php.net

Given that bugsnet has been superseded by GH issues, it is
sufficiently safe to assume that this issue won't be fixed.

------------------------------------------------------------------------
[2018-12-27 11:52:13] 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.

------------------------------------------------------------------------
[2018-12-27 10:54:19] c...@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 04:53:28] 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.



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=77356&edit=1

-- 
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to