[#MISC-2036] Voting Should Not Be Suspended Except When an Entry is Closed

4. Second Life Misc Issues - MISC

Voting Should Not Be Suspended Except When an Entry is Closed

Created: 13/Dec/08 01:55 AM Updated: 14/Dec/08 04:26 PM

Return to search

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Issue Links:

Duplicate

This issue duplicates:

~~WEB-447~~ Allow Votes while "Resolved"

Relates

This issue Relates to:

~~WEB-909~~ Unvote resolved/closed issues

Description

« Hide

It's very clear that "resolved", which has recently undergone some refining and redefinition, is the new "closed".

While a concession has finally been made to recognize that only the author of a bug finding or proposal should be able to close his own entry with his consent, so that it is not closed without his consent (see resolution of ~~WEB-382~~), what we see increasingly frequently now is the use of "RESOLVED" (with "needs more information" or "expected behaviour" to essentially close off and discourage an entry.

That has the undesirable affect of stopping all voting on the entry until the author can be compelled to pay attention, and then, against often considerable peer pressure, he must try to re-open his proposal to get voting started again.

There is no objective reason whatsoever that a JIRA entry cannot continue to attract votes even if someone has decided to mark it "resolved". It certainly doesn't harm the inevitable "clean-up" effort to go on showing the public's attitude to a given entry.

In any event, the entry isn't truly resolved, as we know, because only internal Linden decision-making and absolute resolution leads to true resolution as understood in any system outside this one, where the meaning has become skewed.

This way, even if there is a judgement of "needs more information" or "won't do," authors of entries can still go on soliciting public support. This is vital for the sort of free and democratic scientific inquiry and public participation needed in the JIRA, if it is not to descend into the horrors of Wikipedia.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Gordon Wendt added a comment - 13/Dec/08 10:31 AM - edited

Although I think the resolved is the new closed is somewhat inaccurate since the it's really a matter of educating people about the difference between resolved and closed so that they aren't confusing I actually (oddly) agree with you on this that voting should not be suspended on resolution since this really makes it a pain to deal with bugs (actual software bugs not policy and political "bugs") since often times an issue is resolved as needs more info solely for need of a repro before going up on the triage agenda which makes the number of people effected enough to vote but who don't want to do a "me to" comment much lower than the number of effected people really is.

[ Permlink | « Hide ]

Rob Linden added a comment - 13/Dec/08 12:45 PM

This would need to be fixed in JIRA itself. The feature request is filed here:
http://jira.atlassian.com/browse/JRA-13360

[ Permlink | « Hide ]

Prokofy Neva added a comment - 14/Dec/08 04:26 PM

Rob, as you yourself can see from this link: JIRA originally had this feature of leaving the votes in when an issue was resolved, but then it was taken out. It is very similar to what happened with ~~WEB-382~~, where JIRA had the feature originally not to enable proposals to be closed ultimately except by the author, but it was taken out by LL.

Can you point to any other system that uses this JIRA software not for the making of software itself, which is a rather flat and one dimensional thing, but for the making of a 3-D interactive world with people in it? That is, not to make software that drives applications that run computers, applications for editing, etc. but for a world. And which has feature proposals in it, not about the software itself as that one-dimensional mechanism, but feature requests for a world, i.e. interactive, with people in it.

Remember, I'm not the one who insists on bundling world feature requests together with software bug hunting and findings. I think they should be separate, and the Feature Voting System we used to have before JIRA was fine for this purpose, and could have been improved in various ways, and kept as a separate entity.

I'm going to "unresolve" this because while I realize you "won't do" this, and are citing JIRA itself, I'd like to see if there are votes for this. That's the whole point.

No, Gordon, resolved is the new "closed". And to toss everything back on "user education" is wrong. It's funny how coders want to code every single thing, and in this virtual world, every aspect of human behavior, but as soon as someone wants something coded they don't like, they say "it can't be programmed" and then toss if off to a vague and ineffectual "user education," i.e. hoping that in some haphazard, and unsystematic fashion, people will just "get the message". Of course that doesn't happen, which is why confusion and irritation with the misnomer of "resolution" constantly reigns here.

[ Show » ]

Prokofy Neva added a comment - 14/Dec/08 04:26 PM Rob, as you yourself can see from this link: JIRA originally had this feature of leaving the votes in when an issue was resolved, but then it was taken out. It is very similar to what happened with ~~WEB-382~~, where JIRA had the feature originally not to enable proposals to be closed ultimately except by the author, but it was taken out by LL. Can you point to any other system that uses this JIRA software not for the making of software itself, which is a rather flat and one dimensional thing, but for the making of a 3-D interactive world with people in it? That is, not to make software that drives applications that run computers, applications for editing, etc. but for a world. And which has feature proposals in it, not about the software itself as that one-dimensional mechanism, but feature requests for a world, i.e. interactive, with people in it. Remember, I'm not the one who insists on bundling world feature requests together with software bug hunting and findings. I think they should be separate, and the Feature Voting System we used to have before JIRA was fine for this purpose, and could have been improved in various ways, and kept as a separate entity. I'm going to "unresolve" this because while I realize you "won't do" this, and are citing JIRA itself, I'd like to see if there are votes for this. That's the whole point. No, Gordon, resolved is the new "closed". And to toss everything back on "user education" is wrong. It's funny how coders want to code every single thing, and in this virtual world, every aspect of human behavior, but as soon as someone wants something coded they don't like, they say "it can't be programmed" and then toss if off to a vague and ineffectual "user education," i.e. hoping that in some haphazard, and unsystematic fashion, people will just "get the message". Of course that doesn't happen, which is why confusion and irritation with the misnomer of "resolution" constantly reigns here.