OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [emergency] Web-ex for JIRA usage

Hi Toby,


Thanks very much for your insights shared.  It is nice to know we have a member that can help us through some of the quirks as we go forward with the use of JIRA.





From: Considine, Toby (Campus Services IT) [mailto:Toby.Considine@unc.edu]
Sent: Friday, December 09, 2011 8:22 AM
To: Elysa Jones; emergency@lists.oasis-open.org
Cc: 'Chet Ensign'; dee.schur@oasis-open.org
Subject: RE: [emergency] Web-ex for JIRA usage


I just finished three specifications (WS-Calendar, EMIX, Energy Interoperation) essentially simultaneously, in which two of the three TCs used Jira intensely.


THe discipline of getting each issue into Jira, of classifying it, of having it go through its life-cycle is very useful. It takes a while for a TC to get used to the process. The more each member commits to Jira, the more use it is. I think it sped up our work greatly, while increasing involvement of the diverse group with quite different opinions that were on our team. I think the only ones not happy were the ones who did not use Jira, who may have felt that their opinions were given short shrift. Perhaps this was true, as they did not express them in the consensus process that Jira enables.  The downside, though, is Jira-spam, as it keeps you quite well informed.


Some issues got quite long, as members commented, and re-commented and had quite long discussions in Jira. In some ways this was just as in email comments, but unlike email, it was easy to see the whole thread. Each comment, of course, generated an email to the TC (the afore-mentioned Jira spam).


In particular we had to decide how to use the Jira life-cycle, which can be a little counter-intuitive. We used New for issues not yet being worked. We used “environment” for the source of the comment. While many comments came from TC members, others came, from public comment. With “Sally Commenter” or “Association for Vague Advice” in the same place in each issue, it was easy to assess the viewpoint of the comment, or to run a report to send back to the commenter of all the issues and the resolution of each.


During conversation, we would assign issues to different people to work. Most issues had one person who was most concerned with the issue, even if not most responsible for the resolution. In many cases, this was, of course, the internal member who had raised the issue. After some sort of convergence in the comments, and a proposal was made, we would re-assign the issue to that person, to either move to “resolved” or to comment that the resolution was not acceptable. Of course, some issues skimmed through an abbreviated cycle; no need for much process for syntax errors.


After a while, when we had artifacts to work with, members became used to entering issues first in Jira, and less in email. New open-ended issues still came in email to the list.


When we though an issue was resolved, we would move it to status “resolved” and re-assign it to the person most involved / concerned. We would ask that person to comment by next week (or whatever deadline seemed appropriate). After that time, the relevant editor could apply the resolution to the spec, and move it to “applied”. This gave everyone a chance to review the result before voting as a TC to move it from resolved to closed. Those meeting were usually run with consent agendas, i.e. “42 issues in applied – vote to move to closed, anyone wish to note an exception?”  4 issues held out, all others closed, instant agenda for the rest of the meeting.


There are some annoying life-cycle quirks. One issue is that it can be hard to go backwards, for example, if an issue is marked resolved, and instead becomes contentious, you need to apply/close/re-open/defer if that is what you want. If you look at a new issue and decide no-one cares,  (or that it is unactionable) you can close it directly, but it still shows up on the summary page as “unresolved”. You can get around those issues.


We had a couple members who hung out in the graveyard, reviving closed issues. This was annoying, but worked out for the best. The possibility that this might happen made it possible to move the bulk of issues through faster, and not suspend work merely because someone was absent for a couple weeks.






"It is the theory that decides what can be observed."   - Albert Einstein

Toby Considine

Chair, OASIS oBIX Technical Committee
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Facilities Technology Office
University of North Carolina
Chapel Hill, NC


Email: Toby.Considine@ unc.edu
Phone: (919)962-9073


blog: www.NewDaedalus.com



From: emergency@lists.oasis-open.org [mailto:emergency@lists.oasis-open.org] On Behalf Of Elysa Jones
Sent: Friday, December 09, 2011 5:50 AM
To: emergency@lists.oasis-open.org
Cc: 'Chet Ensign'; dee.schur@oasis-open.org
Subject: [emergency] Web-ex for JIRA usage


TC members,


OASIS TC Admin has agreed to schedule an instructional web-ex on JIRA for those interested members either next Monday 12/12 or 12/13 from 4-5ET.  JIRA is the tool for monitoring and tracking issues.  An overview can be found at http://docs.oasis-open.org/templates/TCHandbook/content/tcoperations/issuestracking.htm.


As our TC currently has Sit-Rep and DE out for public review, CAP-AU within the next few days and HAVE expected in the next month or so, it is prime time for those involved to get a good overview of the JIRA tool to see how it can be a benefit.  We as a TC can decide if, when and how to use the tool, so I’m interested in getting the input of editors, chairs and interested members to guide the decisions we make in this regard.  As we made this decision for Sit-Rep, Rex has been working with it to handle comments recently received and will have input from his use. 


Thanks to Chet and Dee for helping arrange this Web-Ex and to Mark Lucero for proving the dial in number so that Greg from Australia can also participate.  Please respond with your interest and preferred date (Mon or Tues).



Elysa Jones, Chair


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]