Let’s face it. Working in a business environment where tools from multiple vendors are deployed can be challenging. And given the pace at which things move, managing data between different parts of the business can become downright unwieldy. Many of you have shared this challenge with us, and a number of you have partnered with us over the last few months to design a solution which reliably integrates our Rational products with other tools. The wait is over! We are pleased to announce the general availability of the Rational Lifecycle Integration Adapters Standard Edition.Consisting of three integration adapters for HP ALM, JIRA, and Git, this offering opens up new ways for you to share data between tools from different vendors through the power of Open Services for Lifecycle Collaboration (OSLC).
This release also marks a major milestone as Rational’s vision of collaboration across application lifecycle management tools expands to non-IBM products. Many of you may have already begun to experience what these adapters can do by downloading the technology previews made available on jazz.net in June. Whether you have already been collaborating with us on these technologies or are just now discovering this offering, you are invited to join us for a live demo and Q&A session on these adapters on October 25, 2012. We look forward to helping you discover new ways to integrate your diverse business environments!
Find out more about:
- The live demo and Q&A session on October 25: See the “IBM Rational Lifecycle Integration Adapters Standard Edition 1.0 Education Session” listing on the jazz.net Events page
- The Rational Lifecycle Integration Adapters general availability announcement
- The HP ALM, JIRA, and Git adapter technology previews
- Open Services for Lifecycle Collaboration
UPDATE: Recordings of the October 25 demo and Q&A session are now available. They are divided up by adapter (HP ALM, JIRA, and Git), and each lasts approximately 45 minutes. These provide a great overview of the value and basic use cases for each adapter. Take a few minutes and check them out!
HP adapter demo (includes OSLC overview) Speaker: William Jones
Atlassian JIRA adapter demo. Speaker: Joseph Leong
Git adapter demo. Speaker: Steven Wasleski
Brian King
Development Manager
Rational Adapter Development
The link to the “event” is broken
Hi,
During the demo showing the integration between Jira and RTC/RQM/RRC, what are the reasons for doing a mapping between a RRC “feature” and a Jira “New feature” through the “implemented by” OSLC relationship?
-Olivier
Hi Olivier:
About your question:
“What are the reasons for doing a mapping between a RRC “feature” and a Jira “New feature” through the “implemented by” OSLC relationship?”
It sounds to me like there is a misunderstanding of the terms, but also it makes me wonder if you are asking: why do we want to link “requirement” with a “New feature” by the “implemented by” link?
For the first one:
In the Jira video, the demo to link RRC resources with Jira starts at 25:05 m.
In the table that is shown, it is indicated that Jira can be linked to a Rational “requirement”. Is this what you are calling a RRC “feature”?
If so, may be the name “feature” could have been mentioned during the video by mistake. We link Jira “issues” with RRC “requirements”.
In the other hand:
You may want to know why a “requirement” in RRC can be linked to a “New feature” in Jira as the terms may not make sense.
As the table in the video shows, a “requirement” in RRC can be linked to “any type” of Jira issues, even with a “bug”. So far, this is the expected behavior.
You could also propose to add a filter to search for/create a given type of Issue in Jira instead to show all of the types. This way, the LIA team can analyze and discuss the request.
Hope my answer helped you, regards.