RE: [office-requirements] Re: [chairs] OASIS Issues Tracking System

["Mary McRae" <mary.mcrae@oasis-open.org>]

Hi Bob,

  Not yet. I'm hoping that will be the next step. I don't know how much
automation we can do, but at least the comments could go into the general
queue and then be placed into the appropriate "Component" by an Issues
Editor. 

  Regards,

Mary

> -----Original Message-----
> From: Bob Jolliffe [mailto:bobjolliffe@gmail.com]
> Sent: Monday, November 17, 2008 5:33 AM
> To: mary.mcrae@oasis-open.org
> Cc: office@lists.oasis-open.org; office-requirements@lists.oasis-
> open.org
> Subject: Re: [office-requirements] Re: [chairs] OASIS Issues Tracking
> System
> 
> Seconded.
> 
> Am I right in thinking that the comments from the comment list are
> being automatically injected as new Jira issues or is this a manual
> operation?
> 
> If they are being populated automatically and there is more than one
> jira project being fed off one comment list, we do need to have some
> sort of demultiplexing mechanisms - both automatic and manual.  The
> automatic mechanism would kick in when a commenter has included some
> agreed keyword in the subject (say requirements).  The TC might also
> want to manually reassign, similar to Rob's use case below.  I don't
> know if Jira supports exporting an issue from one project and
> injecting it into another as a new issue.  It might be the simplest,
> if not the prettiest, will be to tag the subject line of the original
> comment and resubmit it to the comment list so that the single
> automatic demultiplexing mechanism can do its thing.
> 
> I think it is great to see some progress on tooling.  Congrats.
> 
> Regards
> Bob
> 
> 2008/11/17  <robert_weir@us.ibm.com>:
> > Hi Mary,
> >
> > Thanks for the great new!
> >
> > I'd like to volunteer the ODF TC's ODF Requirements SC's aid in
> helping
> > you define a requirements workflow.  This SC would be a good
> candidate for
> > a beta site of requirements tracking as well.
> >
> > Also, looking at the beta issues tracking workflow, I see that you do
> not
> > have a "refer" state.  As we track comments from the public list, we
> find
> > some that are pertinent to a subcommittees, work such as spreadsheet
> > formulas or accessibility.  When such issues come up on the TC call,
> we
> > refer/transfer/assign them to the SC to propose a resolution.  Is
> there
> > any way to capture that intent in a JIRA workflow?   At first I
> thought we
> > could just assign the issue to the chair of the SC, but that is
> ambiguous,
> > since some members are members of multiple SC's.
> >
> > Similarly, is there a concept of multiple "projects"?  For example,
> if we
> > have a call for comments on ODF Next requirements, simultaneously
> with an
> > ODF Errata review, concurrent with an ODF 1.2 public review, is there
> a
> > way to keep track of issues/comments in a way that keeps these
> distinict?
> >
> > Regards,
> >
> > -Rob
> >
> >
> >
> > From:
> > "Mary McRae" <mary.mcrae@oasis-open.org>
> > To:
> > <chairs@lists.oasis-open.org>
> > Date:
> > 11/17/2008 12:21 AM
> > Subject:
> > [chairs] OASIS Issues Tracking System
> >
> >
> >
> > I am thrilled to announce that the OASIS IT team, in an effort to
> continue
> > to add to the suite of tools available to our Technical Committees,
> has
> > now installed an Issues Tracking system. Thanks to Atlassian, OASIS
> has
> > been granted an Enterprise JIRA license at no cost. You can access
> the
> > system here:
> > http://tools.oasis-open.org/issues/
> >
> > The first ?project? (equivalent to a Technical Committee) has just
> been
> > rolled out with one more in queue. These two projects will be our
> beta
> > testers. if you would like a project created for your Technical
> Committee
> > please send me an email; if all goes well I will start creating
> additional
> > Projects (upon request) the first week in December. All Projects and
> their
> > associated issues are publicly visible (read only). TC Members have
> > read/write access. For the recommended procedure on creating and
> tracking
> > issues please see the help page below.
> >
> > While the Issue Tracking system is fully supported, it is a
> standalone
> > application ? that is, there is no integration with the Kavi system
> for
> > user authentication. This information must be managed manually.
> Similar to
> > Kavi, a user need only be entered once and can be granted (write)
> access
> > to multiple Projects.
> >
> > The help page from the OASIS TC Handbook can be found here (which
> also
> > contains links to the online JIRA documentation):
> > http://docs.oasis-
> open.org/templates/TCHandbook/content/tcoperations/issuestracking.htm
> >
> >
> > There is currently only one workflow ? for issues tracking; I?m
> planning
> > on creating a second workflow for requirements tracking. As always,
> > feedback and suggestions are welcome.
> >
> > Mary
> >
> > ___________________________________________________________
> > Mary P McRae
> > Director, Technical Committee Administration
> > OASIS: Advancing open standards for the information society
> > email: mary.mcrae@oasis-open.org
> > web: www.oasis-open.org
> > phone: 1.603.232.9090
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  Follow this link to all your TCs in OASIS at:
> > https://www.oasis-
> open.org/apps/org/workgroup/portal/my_workgroups.php
> >
> >
> > --
> > This message has been scanned by DST MailScanner
> >
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php