<div dir="ltr">I like the needs info for sure, I've wanted to go as far as heuristic tests to auto detect that it needs info ;)<div>The auto resolve from that state is a good one too.</div><div><br></div><div>We should for sure make better categories than we have for bounty or things that are cool but there is no time to do.</div>
<div>Right now we have a user who's name is "make me stuff for free" and we assign them to him so that can be improved.</div><div><br></div><div>The 5 for 1 thing is good, It would be great to get everyone just doing it naturally where they can learn to scan a jira in a once-over and be able to tell what else it needs. </div>
<div><br></div><div>I'm also interested in maybe some way to get the policies and other info visible to the users so we don't have to keep repeating so many things.</div><div><br></div><div><br></div><div><br></div>
<div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 15, 2013 at 11:07 AM, Cal Leeming [Simplicity Media Ltd] <span dir="ltr"><<a href="mailto:cal.leeming@simplicitymedialtd.co.uk" target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<div><br></div><div>Last week I made some contributions on JIRA by triaging some tickets.</div><div><br></div>
<div><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">
<div>FS-3964 - requested larger bounty offer, if no bite then reclassify as nice to have</div><div>FS-4211 - requested further info, close after 2 weeks if no response.</div><div>FS-4281 - requested more info, waiting on core devs</div>
<div>FS-4891 - requested more info, updated wiki docs, close after 2 weeks if no response</div><div>FS-5154 - requested OP create new ticket for seperate issues, close after 2 weeks if no response</div><div><br></div><div>
However, I was unable to action them due to lack of access on JIRA. I sent an email to Ken/Michael requesting access to close tickets and mark as resolved etc, but realised this was not the appropriate way as you shouldn't need to have extra privileges in order to do ticket triage.</div>
<div><br></div><div>Therefore, I'd like to open up discussion about how we can improve JIRA to allow for public contributions and make ticket triaging easier.</div><div><br></div><div>My suggestions are;</div><div><br>
</div><div><div>* Add a new step in the workflow that switches it into "needs more client info", so it automatically closes the ticket after X days if no extra info is received.</div><div>* Have a "maybe one day/needs contributions" status in the workflow, rather than leaving the ticket as open.. that way we can see really how many are waiting, and how many are waiting on contributions.</div>
</div><div>* Have a "needs design decision" status in the workflow, indicating that a core dev needs to make the final call</div><div>* Introduce an official 5-for-1 ticket system where users can triage 5 tickets and request that a core dev look at any ticket of their choice in return.</div>
<div><br></div><div>I think we stand a much better chance of getting a lot more public contributions if we implement these changes.</div><div><br></div><div>Probably a bit too short notice to discuss on todays conf call, but it would be good to get some ideas/feedback in time for next weeks call. Modifying JIRA and making workflow changes is no easy task, so it would need to be thoroughly discussed and understood. I'll be on the call today 20 minutes early today if anyone wants to discuss. </div>
<div><br></div><div>Any thoughts/ideas?</div><div><br>Thanks</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Cal</div></font></span></div></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900
</div>