Last modified: 2011-11-30 14:54:45 UTC
I'm sure there is some kind of workflow reason for developers to have this redirect behaviour, however it is unlike any kind of client or website I have ever used (see email, forums, any other bug/help reporting system that deals with end users). It was incredibly confusing at first and invariably as a person reporting bugs, I click back to the bug I posted to and ensure my comment rendered correctly etc. This also means my tab is ready for me to refresh to check for updates (or when I get an email without having to click a link and open yet another window). While developers are likely used to the behaviour now, and developers may find it a convenience, it hampers communication with new users and makes filing bugs confusing and hard to use. We should be making it as easy as possible on the bug reporters, even if that means a bit more work for the fixers.
(In reply to comment #0) > I'm sure there is some kind of workflow reason for developers to have this > redirect behaviour, however it is unlike any kind of client or website I have > ever used (see email, forums, any other bug/help reporting system that deals > with end users). > What redirect behavior are you talking about? This bug report doesn't describe the observed behavior at all, which is very confusing.
It was in the topic?
Test
This is a user preference, "After changing a bug" which I set the default to now be "Show the updated bug." If someone wants the old behavior, they can change their preference :)