Re: [chairs] OASIS Issues Tracking System

[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