[TYPO3-bugs] Discussion: Close vs. resolve in Mantis Bugtracker

[Franz Holzinger]

Francois Suter a écrit :

>> which IMO is wrong as they of course are dulicates, but they're still 
>> a sort of bug (duplicate extends bug). Therefore I'm for handling them 
>> the  same way as we do with all ther bugs (see above), resolve them 
>> when their original bugs are resolved, close them when their original 
>> bugs are closed.
> 
> Duplicates still leave quite me perplex from time to time. The main 
> problem for me is that duplicate relations go both ways. On the one hand 
> with is pretty logical, but on the other hand it makes hard to find 
> which "copy" is being worked on. It should be possible to mark which bug 
> is the "original". In that sense closing duplicates is not a bad 
> solution. Maybe we need to come up with a new status however.

3. Resolve bugs when fixed, have the reporter close them when fix is
    confirmed (as proposed by the Mantis developers in their manual)
+1

Reason: Bugs are sometimes closed to early. The developer cannot tell 
exactly what the reason for a bug has been. It should be closed 
automatically after 6 months when no feedback comes.
Other persons should still be able to write comments to existing bugs 
and not be forced to recreate the same issue again, when the same bug is 
still present. And unfortunately they are not able to mark a bug as the 
duplicate of another one.

- Franz