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

[Michael Stucki]

Hi Ernesto,

>>> For example, Ernesto resolves bugs after fixing them, but in case of a
>>> duplicate issue, he closes them directly.
>> 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.
> 
> I would be ok with that (if everybody agrees), but then it is important
> that the guy that "resolves" the one issue that has "dozens" of
> duplicates also updates the information about "fixed in version" on all
> duplicate entries. Else it will be difficult to keep track of what was
> really resolved on which release.

Agreed. As Ingo already pointed out, this is already possible but it may
be that some of us haven't used that feature.

So I propose to update the "Managing bugs" page on typo3.org and add the
following paragraph:

If a bug entry is identified as a duplicate of another issue, it will be
marked resolved, resolution "duplicate" and with the duplicate ID filled
in the appropriate field. The properties "duplicate of" and "has
duplicate" must be used properly so that only one issue needs to remain
open until the issue is fixed.

http://typo3.org/development/bug-fixing/managing-bugs/

If everyone agrees about this, I think there's no need to vote any more.
 Any vetos to this?

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/