Hi all,<div><br></div><div><div>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.</div><div><br></div><div>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.</div>
<div><br></div><div>Thanks</div><div><br>Cal</div><br><div class="gmail_quote">On Thu, May 16, 2013 at 1:56 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">Hi guys,<div><br></div><div>Thanks for taking the time to discuss this on the call today.</div><div><br></div><div>I think the general outcome can be summarized as;</div>
<div><br></div><div>* 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</div>
<div>* JIRA needs to be improved, and internal discussions will take place to find way for this to be done.</div><div>* 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.</div>
<div>* Keep calm and carry on, all contributions no matter how small are very much welcomed and appreciated</div><div><br></div><div>If anyone else has any suggestions on how things can be improved, put your ideas into this thread whilst it's still hot!</div>
<div><br></div><div>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.</div>
<div><a href="http://wiki.freeswitch.org/wiki/UsingTheMailingList" target="_blank">http://wiki.freeswitch.org/wiki/UsingTheMailingList</a></div><div><br></div><div>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.</div>
<div><br></div><div>Thanks guys</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Cal</div></font></span><div><div><br></div><div><div class="gmail_quote"><div class="im">On Wed, May 15, 2013 at 5:07 PM, 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>
</div><div><div class="h5"><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><font color="#888888"><div><br></div><div>Cal</div></font></span></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>