Your first suggestion is already available. That's what I do every single day and most of the times, I get no response and tickets get closed automatically. I guess that more than doing triage we lack the human power to reproduce on a controlled environment the tickets that get unattended... Just my 2 cents João Mesquita FreeSWITCH™ Solutions On Wed, May 15, 2013 at 1:07 PM, Cal Leeming [Simplicity Media Ltd] < cal.leeming@simplicitymedialtd.co.uk> wrote:
Hello all,
Last week I made some contributions on JIRA by triaging some tickets.
FS-3964 - requested larger bounty offer, if no bite then reclassify as nice to have FS-4211 - requested further info, close after 2 weeks if no response. FS-4281 - requested more info, waiting on core devs FS-4891 - requested more info, updated wiki docs, close after 2 weeks if no response FS-5154 - requested OP create new ticket for seperate issues, close after 2 weeks if no response
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.
Therefore, I'd like to open up discussion about how we can improve JIRA to allow for public contributions and make ticket triaging easier.
My suggestions are;
* 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. * 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. * Have a "needs design decision" status in the workflow, indicating that a core dev needs to make the final call * 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.
I think we stand a much better chance of getting a lot more public contributions if we implement these changes.
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.
Any thoughts/ideas?
Thanks
Cal
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org