barlowm/RTT_GITHUB_Integration.txt

## RTT_GITHUB_Integration.txt
IBM RATIONAL IMPLEMENTATION
GITHUB Integration, RTC & RQM Schema Changes
Title: GRAPHIC SAYING UPGRADE - Description: THIS IMAGE IS JUST THE WORD UPGRADE, WITH THE LETTER USE HAVING AN UP ARROW.

The IBM Rational Tools Team is announcing the availability of repository integration between Rational and the VA ECSO implementation of Github using Enterprise Git for teams that are using or are planning to use Github for source code control while their project requirements, sprints, change, status, test and other tracking data continues to reside within Rational.
The Rational Team has also implemented multiple Rational Team Concert (RTC) schema changes which were requested from users as well as a new custom report for Rational Quality Manager (RQM).

Integration Between Rational and Github

Your existing or new Rational Team Concert repository can be re-configured to allow your team to use a Git repository for source code rather than the source control native to Team Concert.  This is done by educating your Team Concert configuration about the direct link to your Github repository, and by placing a configuration file in your Github repository that understand specific keywords that will execute notification actions between the two repositories so that actions in Github to update source code content will report status back to Rational.
To implement the integration between the two repositories, please file a Rational Service Request (http://go.va.gov/rational-sr)  and we will work with your team on the transition of your source code and the configuration changes to activate the interface.
For more information about the interface, please email rational@va.gov and we will provide an orientation document about the integration.


New Team Concert Schema Changes

Traceability Indicator:
A new, optional, drop-down list field on Epics, Stories, Tasks, and Defect named Traceability Indicator has been added. This provides an indication of the traceability requirements for this work item, with values available of Functional, Technical, and Dev Supporting. The form has a hover-link for the field to show users what the values are used for, with examples.
Deferred Work Items:
The workflows of all work items that have the status Deferred have been updated. This changes the status group for Deferred work item to be considered Open, not as was previously Resolved. This will allow children work items of Deferred work items to be left open, since Deferred work is not actually done.
VIP Risk Log:
The VIP Risk Log query has been updated to be more useful to those who run it. Instead of asking for very detailed filters, it will start filtering by team instead of iteration.
Acceptance Test Field:
On the Story work item type, when the status is set to Ready for Review, the Acceptance Test field is mandatory. Having the Acceptance Test written for the Story will help the testers confirm that the Story passes when they perform the testing and reviews.
Found In Field:
On the Defect work item type, the field Found In is mandatory when submitting the defect and in all statuses going forward. This field is based on the drop-down list called Releases, which can be maintained by the Scrum Master or Product Owner. Recording the release version that the Defect was Found In will assist developers in debugging and correcting any defect found.
DE&A Compliance Evidence Verified:
On the Release Readiness work item type, a new measurement called DE&A Compliance Evidence Verified was added to confirm release readiness. In addition, some form labels were cleaned up and the terminology was changed for the status of the record: Recommended has become Ready, and Not Recommended has become Not Ready. The Release Agents are using different terminology in their audits, so the new wording is reflected in the Release Readiness record.
New Deployment Request Work Item Type:
A new work item type has been added called DR, which stands for Deployment Request. The DR work item is used to track requests, approvals, build information, etc. for deployments to each environment. The DR work item would include all build information for what is being deployed, and teams could more easily implement an approval process with the customer or environment owner, providing more traceability on when and what is deployed and to where.

New Quality Manager Custom Report

The IBM Rational Implementation Team has created a custom report, Full Test Plan Details Report, for Quality Manager users.  This report allows users to better visualize the testing management elements Test Plans, Test Cases, Test Scripts and Test Steps in a tabular view.
More Information on the Report:

Go to: http://go.va.gov/rational
Click on the Documentation tab (on the top line of links) or the Documents link on the left side of the page.
Expand the outline for Document Category: RQM Procedures to see the list of documents
Click on the link for ‘How_to_Run_Full_Test_Plan_Details’ to open/save a PDF file and provide you step-by-step instructions on access to the report from within Quality Manager.

Please contact us if questions.
rational@va.gov
http://go.va.gov/rational
	IBM RATIONAL IMPLEMENTATION
	GITHUB Integration, RTC & RQM Schema Changes
	Title: GRAPHIC SAYING UPGRADE - Description: THIS IMAGE IS JUST THE WORD UPGRADE, WITH THE LETTER USE HAVING AN UP ARROW.

	The IBM Rational Tools Team is announcing the availability of repository integration between Rational and the VA ECSO implementation of Github using Enterprise Git for teams that are using or are planning to use Github for source code control while their project requirements, sprints, change, status, test and other tracking data continues to reside within Rational.
	The Rational Team has also implemented multiple Rational Team Concert (RTC) schema changes which were requested from users as well as a new custom report for Rational Quality Manager (RQM).

	Integration Between Rational and Github

	Your existing or new Rational Team Concert repository can be re-configured to allow your team to use a Git repository for source code rather than the source control native to Team Concert. This is done by educating your Team Concert configuration about the direct link to your Github repository, and by placing a configuration file in your Github repository that understand specific keywords that will execute notification actions between the two repositories so that actions in Github to update source code content will report status back to Rational.
	To implement the integration between the two repositories, please file a Rational Service Request (http://go.va.gov/rational-sr) and we will work with your team on the transition of your source code and the configuration changes to activate the interface.
	For more information about the interface, please email rational@va.gov and we will provide an orientation document about the integration.


	New Team Concert Schema Changes

	Traceability Indicator:
	A new, optional, drop-down list field on Epics, Stories, Tasks, and Defect named Traceability Indicator has been added. This provides an indication of the traceability requirements for this work item, with values available of Functional, Technical, and Dev Supporting. The form has a hover-link for the field to show users what the values are used for, with examples.
	Deferred Work Items:
	The workflows of all work items that have the status Deferred have been updated. This changes the status group for Deferred work item to be considered Open, not as was previously Resolved. This will allow children work items of Deferred work items to be left open, since Deferred work is not actually done.
	VIP Risk Log:
	The VIP Risk Log query has been updated to be more useful to those who run it. Instead of asking for very detailed filters, it will start filtering by team instead of iteration.
	Acceptance Test Field:
	On the Story work item type, when the status is set to Ready for Review, the Acceptance Test field is mandatory. Having the Acceptance Test written for the Story will help the testers confirm that the Story passes when they perform the testing and reviews.
	Found In Field:
	On the Defect work item type, the field Found In is mandatory when submitting the defect and in all statuses going forward. This field is based on the drop-down list called Releases, which can be maintained by the Scrum Master or Product Owner. Recording the release version that the Defect was Found In will assist developers in debugging and correcting any defect found.
	DE&A Compliance Evidence Verified:
	On the Release Readiness work item type, a new measurement called DE&A Compliance Evidence Verified was added to confirm release readiness. In addition, some form labels were cleaned up and the terminology was changed for the status of the record: Recommended has become Ready, and Not Recommended has become Not Ready. The Release Agents are using different terminology in their audits, so the new wording is reflected in the Release Readiness record.
	New Deployment Request Work Item Type:
	A new work item type has been added called DR, which stands for Deployment Request. The DR work item is used to track requests, approvals, build information, etc. for deployments to each environment. The DR work item would include all build information for what is being deployed, and teams could more easily implement an approval process with the customer or environment owner, providing more traceability on when and what is deployed and to where.

	New Quality Manager Custom Report

	The IBM Rational Implementation Team has created a custom report, Full Test Plan Details Report, for Quality Manager users. This report allows users to better visualize the testing management elements Test Plans, Test Cases, Test Scripts and Test Steps in a tabular view.
	More Information on the Report:

	Go to: http://go.va.gov/rational
	Click on the Documentation tab (on the top line of links) or the Documents link on the left side of the page.
	Expand the outline for Document Category: RQM Procedures to see the list of documents
	Click on the link for ‘How_to_Run_Full_Test_Plan_Details’ to open/save a PDF file and provide you step-by-step instructions on access to the report from within Quality Manager.

	Please contact us if questions.
	rational@va.gov
	http://go.va.gov/rational