21.04.2016, 14:35, Andy Seaborne wrote:
I'd like to open a discussion on what is and is not a reasonable JIRA so
that we can close ones that are outside what JIRA is good for.
+1
I closed this on the principle that repeatedly asking the same question
in many places in just a few hours is unhelpful.
Makes sense. Though from an outsider perspective, it may not be obvious
that for example StackOverflow is being watched by the same people who
also see the JIRA issues.
In this particular case the symptom was a NPE, which could indicate a
bug, so opening a JIRA issue for it is OK. But I don't think it makes
sense to maintain both an SO question and a JIRA issue, and in my
understanding SO questions cannot be closed with a "tracked on JIRA", so
closing the JIRA and leaving the SO question in place was probably the
right thing to do.
I think we need to not allow JIRA items that cause additional work, are
"reproducable", or a really questions.
If we get ones that are questions, direct to mailing lists without
answer on JIRA. (does not apply so much to this is one)
if they don't have a complete, minimal example, ask for one, once. If
none is forthcoming, close the JIRA. It can take significant time to
figure out what a test case is and that time is taken away from
answering other questions.
+1 (Assuming you meant not reproducible, as Adam already pointed out)
It might be useful to establish a deadline for additional information
(i.e. defining what "none is forthcoming" means in practice). It could
be, say, two weeks or a month from asking.
-Osma
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
[email protected]
http://www.nationallibrary.fi
