In Release 14, the RFE Community lets you associate requests. If requests have similar enhancements or capabilities, the RFE Community allows you to associate a request with another request. Examples of these request associations are:
- When there is a dependency between requests
- When requests are similar, but may have different enhancement or capability details
Customer tracking ID
The customer tracking ID is an ID that may be used in a customer's internal database system. The RFE Community allows you to enter the Customer ID in the request to help you easily track requests and avoid request duplications. This field is private and is only accessible to the request submitter.
Search by RTC and ROCR ID
Release 14 of the RFE Community introduces a new search option for requests. Previously, you could only search for requests using the RATLC number or request ID. Now, you can also search using the the ROCR ID and the RTC ID. The ROCR ID is the ID assigned to an entry in the Rational ClearQuest database. This is only for Rational products. The RTC number is the ID assigned to an entry in the Rational Team Concert database. This is for most brand requests. A request ID is the ID assigned to a request entered directly in the RFE Community. All requests get an RFE Community request ID assigned.
- Find out more about the RFE Community.
- developerWorks blogs: Check out developerWorks blogs and get involved in the developerWorks community.
Dig deeper into developerWorks
Get samples, articles, product docs, and community resources to help build, deploy, and manage your cloud apps.
Keep up with the best and latest technical info to help you tackle your development challenges.
Software development in the cloud. Register today to create a project.
Evaluate IBM software and solutions, and transform challenges into opportunities.