Hi Sharan, All, Please see inline.
Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Fri, Jul 15, 2016 at 11:53 AM, Sharan Foga <sharan.f...@gmail.com> wrote: > Hi All > > We have an amazing number of Jiras open and because we have so many it's > getting very confusing as to what are the priorities and things are getting > clogged up. > > I've got a few initial ideas and suggestions that could maybe help improve > the workflow > We should differentiate between bugs and the other types of JIRA issues (improvement, new feature and wish) for single or placeholder issues. The latter type is a depiction of a potential future scenario (improvement being closest to now - direct related to existing code and wish being the farthest away) intended to enhance the user experience with new functionality. So, here I am focussing on the issues typed as Bug in JIRA. > > 1) Highlight Parked / On Hold Jiras > We have quite a few Jira issues that are 'parked' or 'on hold' – so it > would be good if these were clearly identified so that if people come > across them they know that they are not being worked on (and the reason). > > We could look at adding a new status, a flag or a label that could hold > this information. > Not all bugs are equally important. That is why we have the Priority field, with a limited set of choices. But there is a difference in impact. A bug might be of a technical nature, which is easy to prove with an error report. Or it might be of a business nature: it works fine technically, but is unacceptable in a particular business domain due to GRC policies and procedures. I refer to OFBIZ-7796 <https://issues.apache.org/jira/browse/OFBIZ-7796>, OFBIZ-7767 <https://issues.apache.org/jira/browse/OFBIZ-7767> and OFBIZ-7783 <https://issues.apache.org/jira/browse/OFBIZ-7783> as examples. Some will call these improvements as well, but these kinds of issues put a serious barrier regarding adoptability. So my suggestion is to be able to classify better: e.g. add 'business' and 'techinal' as choices to the mix. > > 2) QA Review for New Jiras > I think it would also be good to look at introducing some type of review > stage for newly created issues. This also could give us a bit of QA to make > sure that there is enough information needed for the task to be worked on. > It could also be then allocated to a workstream. > > 3) Define Workstreams > We have a good idea of the areas that we want to focus so it should be > relatively easy to setup some workstreams. I'd like to explore the idea of > workstreams a bit more because it could be something that could be an > entire sprint, an issue category or it could be the equivalent of a planned > future release. > > I know Jira allow us to define a Roadmap and versions and that we already > have something setup that helps us with our release management > (I.e.automatically incorporates all the Jiras applied to a version) that we > don't want to break – so this might need more investigation > > https://www.youtube.com/watch?v=7GL6LH6ufhM > 4) Review of Old Jiras > One of things that we've had hanging around for ages is a lot of old > Jiras. At the moment I think Jacques takes on a few at a time, so it could > be good to get some other volunteers and start looking at these and either > closing them, parking them or allocating them to a workstream. > I have been reviewing old issues regularly over the past few years, and some I could help move forward. It is a tedious job, but one must not shy away from it. Each contributor can start with the ones he assigned himself to. And then work his way, slowly but surely through the list of issue related to the subject he cares about. I remember us having a wiki page indicating who was interested in what and who was willing to work on what. A page I now can't find that easily. Maybe we could revisit that and see if we can bring that back to life. > > These are a few of the ideas I had in mind – the main objective is to make > Jira into a useful tool for help us with our workflow. > > Please feel free to let me have your feedback and comments, and if anyone > else has other ideas and suggestion to share, then please do. > Thanks for sharing. Great initiative. > > Thanks > Sharan > >
