I wonder how Mike McCandless extracts the information for http://jirasearch.mikemccandless.com/search.py?index=jira
Because some of the reports discussed seem like they would be very easy against what he built. Or even if that extracted and transformed information could be available as a bulk download to play with instead of trying to wrestle JIRA REST API. Regards, Alex. ---- Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/ On 29 September 2016 at 19:01, Stefan Matheis <ste...@mathe.is> wrote: > On September 29, 2016 at 12:05:12 PM, Dawid Weiss (dawid.we...@gmail.com) > wrote: >> > As a project I feel it is unnecessary to have 2933 unresolved issues in >> > JIRA. >> >> Some of these are old ideas, but remain valid (and are still >> unresolved), Jan. This has been discussed in the past without clear >> resolution. >> > > Which is absolutely fine - at least how i understand Jan’s suggestion. The > point would probably be to revisit those from time to time and decide if they > are still valid or perhaps already done as part of another ticket or > something along the lines. > > > On September 29, 2016 at 11:53:37 AM, Jan Høydahl (jan....@cominvent.com) > wrote: >> Furthermore the time to first response is not uncommonly 90 days or more! >> I think we should strive to have no newly opened issues older than 7 days >> without at least having one response, question, +1/-1 etc. Perhaps with >> the exception of issues created by the committers or assigned to someone? > > I like it. I’m not even sure i’d make an expection for issues that are > assigned to someone - especially new users tend to use JIRA in ways we > probably are not aware of (including setting an estimate and stuff like that) > > > first idea about it: we could bring a script or something that collects once > a week information about all new issues and sends it to the dev-list? so get > a quick overview about what happend last week w/o too much trouble? > > -Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
