Based on the points raised in the discussion maybe there is scope to have some ground rules for open tickets. Something like:
A ticket can be closed if: - no activity for 12 months. - no response from the reporter to requests for information for 12 months. Applying this may mean we have a better chance of seeing the wood for the trees so to speak. What does everyone think? Cheers, Andrew On Wednesday, October 23, 2013, Daniel Beck wrote: > Is there a guideline how to use the Jenkins Jira as a regular user? > > I've seen many issues that seem obsolete, incomplete, or just plain wrong > (this feature not being implemented is not a bug!), but I've always > hesitated to just close or relabel them, especially when it's about a > plugin, as I'm no more an authority on what's a valid issue than the guy > that opened it. On Stack Overflow, I'd "flag for moderator attention", but > there's no such feature in Jira. > > [1] doesn't cover what seems to be the most common case, a reporter not > responding to questions in comments, or any other situations unrelated to > reproducing an issue or verifying a fix. > > 1: > https://wiki.jenkins-ci.org/display/JENKINS/Beginners+Guide+to+Contributing > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:;>. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
