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

Ernesto Baschny [cron IT] ernst at cron-it.de
Fri Oct 31 19:49:42 CET 2008


Ingo Renner wrote: on 31.10.2008 19:16:

>> 1. Resolve bugs when fixed, close bugs when the fix has been released
> 
> +1, this is how we did it until now and what I feel is correct
> 
>> Additionally, opinions vary whether this applies to all sorts of issues,
>> or if it should be treated differently depending on the state of
>> resolution.
>>
>> 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.

To put in another words: We need to make sure that those issues resolved
(because they where "duplicates") are properly closed when the original
issue is closed at the moment we release the product.

Cheers,
Ernesto


More information about the TYPO3-team-bugs mailing list