|
|
|
About the voting part, that's not really what I meant - to reword, is there any situation where voting on a something shouldn't automatically reopen it? If not, then there would be the (possibly easier) option of just telling people to reopen and then vote, or creating a single reopen-and-vote button.
I'm pretty sure this isn't something that LL can configure in JIRA. That means it should be filed as a feature request with Atlassian (the makers of JIRA) directly. Look at the bottom of any page and follow the "Bug/feature request" link.
The specific implementation might not be doable, but we might be able to get something that does near the same thing. (see first comment above)
Thank you Celierra! We agree that voting on Resolved issues is something we'd like to have. Being that this is a feature that Atlassian would need to add, please add your votes here: http://jira.atlassian.com/browse/JRA-13360
 .
If and when they add this feature, we will add it to our Pjira. I am watching this issue and will re-open this if there is any progress. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Sub-task
Resolved
Normal
Of course you need to keep votes open on this "pending" or replacement of "resolved". That's the whole point. To end the ability of the small group of "caretakers" to go around closing everything off and destroying its vote-gathering process. That is indeed the entire point. Notification on email, especially given that these automatic JIRA notices come into bulk email half the time or discussion notions are too numerous to sort through, is not insurance that a person will wake up and realize their votes are being frozen.
No, there is absolutely no reason to shut off votes on a proposal EVER until it reaches it's final state of death, which is when, with the consent of the author, it is closed. "Won't finish" strikes me as a Lindenized argument and ought not to freeze voting, either, but this is a separate discussion.
Of course people will go on voting on issues that one of the small group has decided to arbitrarily close as not to his liking – as this "motion for resolution" or "motion for closure" (that's all it is; it is no longer an actual closure under my proposal" is merely a signal of somebody getting up in their grill about something, it can be safely ignored OR if there are rational debates or handy demonstrations of duplicate status, it can be dealt with quickly by the author.