This is Altassian Jira. We have recently implemented Jira for
our tracking system and love it. Its very powerful, easy to use and flexible.
I think it would be a great way for us to track our action items and a way to
record back log items.
From: Brent Miller [mailto:email@example.com]
Sent: Monday, November 17, 2008 1:35 PM
Subject: [sdd] Fw: [chairs] OASIS Issues Tracking System
Please have a
look at this new tool and let me know if you think it has value for our TC.
Brent A. Miller
Technical Staff Member
Chief Architect, Tivoli Autonomic Computing & Component Technologies
919-543-6959 (TIE 441)
theory, there is no difference between theory and practice.
But, in practice, there is."
-- Jan L.A. van de Snepscheut
Forwarded by Brent Miller/Raleigh/IBM on 11/17/2008 07:34 AM -----
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:
“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.
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):
currently only one workflow – for issues tracking; I’m planning on creating a
second workflow for requirements tracking. As always, feedback and suggestions
Mary P McRae
Technical Committee Administration
Advancing open standards for the information society