Comment 2 for bug 3136

Me too. I doubt any uninitiated user of Malone could figure out how to do change status without trying lots of links and getting frustrated (and the one uninitiated user I have watched did exactly that). I still half-expect that link to take me to the product page, and I'm used to it :)

The fact that a bug can be associated with multiple upstreams or packages isn't immediately obvious, and isn't expected (other systems don't do that), so the fact that Malone tracks status in the bug tasks and not the bug is not clear unless we really emphasise it. Adding the proposed "Change Status" link would help here. This is especially true for the majority of bugs in Malone with only a single bug task.