On 10/22/2013 12:50 PM, Daniel Beck wrote:
Is there a guideline how to use the Jenkins Jira as a regular user?
Sounds like the question is more about how to use it as a developer.
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.
I'd say you should go ahead and make these updates. You spent the cognitive effort groking the issue, we should leave that in the record.
Nothing you do in the issue tracker is irreversible. If other people disagreed they just need to reopen or reroute the ticket.
Except in a few plugins where there's a clear de-facto owner, plugins do not have any "authoritative source" more often than not.
[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
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- 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.
