[TYPO3-dev] passwords can't be changed in 4.2.2 backend

[Ernesto Baschny [cron IT]]

Michael Stucki wrote: on 19.10.2008 14:58:
> Hi Ernesto,
> 
>>> I still prefer resolved status over having bugs disappear right away.
>>> What do you think is wrong with that?
>> What do you mean "disappear"? In the search it is up to you which
>> filteting you want on the status. You can remove the filter on "status"
>> altogether, and then even closed issues appear. I have "Hide status" =
>> "resolved (and above)", meaning even resolved issues won't appear.
> 
> We are talking about the average user who doesn't change the presets and
> just searchs for some words. If the bug is closed, he will not find it.
> 
> I just had exactly the same problem and did not find bug #9494 although
> I searched for "undefined". When I changed the filter to show the closed
> issues too, I finally found that the issue is still pending as part of a
> different issue (#9497).
> 
> Meanwhile some other user did exactly what I mentioned before in this
> thread and created a new issue #9597 which was about exactly the same.

That is a problem with the current setting (hiding "Closed" by default).
I would change that so that anonymous and "new" users also see that kind
of bug reports. Because that way we can argue that no bug should be ever
"closed", as that will always filter out important bug reports ("Won't
fix", already fixed in current releases, etc).

>> In my eyes the dupes distract from the real important stuff.
> 
> They don't but they help to find stuff more easily. Of course all
> resolved issues will still be changed to closed right after every release.

How would the release manager do that? If you set a duplicate bug to
"resolved" (with Resolution="Duplicate") the release manager cannot be
sure if it has been fixed for his release or not. He will have to check
each one of them, if the bug (or one of its "duplicates") have been
really "resolved" in the meantime before a release or not.

Last time that kind of stuff was "cleaned" was in the "bug day", where
someone manually went over the resolved bugs and "closed" them (Benny
and Ingo). That hasn't happened before any release yet. This "manual
cleanup" shouldn't be needed, in my eyes.

> Conclusion: Please keep doing it the old way and mark duplicates as
> resolved. They will be found by all users (because resolved i not
> excluded by default) and everyone can read the comments to see why a bug
> was marked "resolved". It is important that all of us treat bugs the
> same way, otherwise it will confuse users even more...

Exactly. I expect that the majority of us bug fixers have been closing
duplicate bug reports forever now, me included. It has even been
suggested to do so years ago
(http://wiki.typo3.org/index.php/Bugfixing_Team).

So maybe we should "vote" on that matter? I agree we should be handling
that the same manner, and would gladly do it in another way, if I feel
that the majority also wants to do it.

Cheers,
Ernesto