JIRA contributions - 15/05/2013
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
I like the needs info for sure, I've wanted to go as far as heuristic tests to auto detect that it needs info ;) The auto resolve from that state is a good one too. We should for sure make better categories than we have for bounty or things that are cool but there is no time to do. 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. 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. 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. On Wed, May 15, 2013 at 11:07 AM, 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
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
Hi guys, Thanks for taking the time to discuss this on the call today. I think the general outcome can be summarized as; * The 5-for-1 approach would need internal discussion before being officially adopted, however some core devs would be willing to participate prior to that happening, on a case-by-case basis * JIRA needs to be improved, and internal discussions will take place to find way for this to be done. * If you cannot triage a ticket due to lack of access, add your comments with the suggested action so a core dev only had to spend a few seconds on the ticket, rather than a few minutes in triage. * Keep calm and carry on, all contributions no matter how small are very much welcomed and appreciated If anyone else has any suggestions on how things can be improved, put your ideas into this thread whilst it's still hot! In the mean time, I have added an unofficial '5-for-1' section into the mailing list with some general guidelines on how to request this, and made it clear that this is not an officially adopted approach yet so YMMV etc. http://wiki.freeswitch.org/wiki/UsingTheMailingList If there is anyone here that wants to contribute but doesn't know where to start, speak up now! Tell us what you want to know, and what we can do to help you contribute. Thanks guys Cal On Wed, May 15, 2013 at 5: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
Hi all, Triaged a couple more tickets today, but came up against the same problem of the system not marking the ticket as "waiting on reporter" after triage. Has any more work been made on improving the JIRA workflow to make public triage a bit easier? I think in this situation, just having a button that allows us to move the ticket into a "waiting on reporter" or "waiting on core dev" state would suffice.. for now I'll leave my suggested action in the comments of the ticket, so when a core dev or triage team member comes along, they can deal with it much quicker. Thanks Cal On Thu, May 16, 2013 at 1:56 AM, Cal Leeming [Simplicity Media Ltd] < cal.leeming@simplicitymedialtd.co.uk> wrote:
Hi guys,
Thanks for taking the time to discuss this on the call today.
I think the general outcome can be summarized as;
* The 5-for-1 approach would need internal discussion before being officially adopted, however some core devs would be willing to participate prior to that happening, on a case-by-case basis * JIRA needs to be improved, and internal discussions will take place to find way for this to be done. * If you cannot triage a ticket due to lack of access, add your comments with the suggested action so a core dev only had to spend a few seconds on the ticket, rather than a few minutes in triage. * Keep calm and carry on, all contributions no matter how small are very much welcomed and appreciated
If anyone else has any suggestions on how things can be improved, put your ideas into this thread whilst it's still hot!
In the mean time, I have added an unofficial '5-for-1' section into the mailing list with some general guidelines on how to request this, and made it clear that this is not an officially adopted approach yet so YMMV etc. http://wiki.freeswitch.org/wiki/UsingTheMailingList
If there is anyone here that wants to contribute but doesn't know where to start, speak up now! Tell us what you want to know, and what we can do to help you contribute.
Thanks guys
Cal
On Wed, May 15, 2013 at 5: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
participants (3)
-
Anthony Minessale
-
Cal Leeming [Simplicity Media Ltd]
-
João Mesquita