Resource Traceability configuration checklist

Resource Traceability gives Polarion users the power to link source code assets semantically. (Link Work Items directly to the source code function, method or variable that implements them.)

This gives managers and auditors a traceable record of all implemented changes and developers a link to who and what prompted a task, in case further clarification is required.

Developers simply add a custom comment to the source code they’re developing and it is automatically parsed to any Work Item (Requirement, Change Request, Improvement, Bug Fix etc.) that the code implements.

Administrators can configure how and when this information is parsed in multiple configurations, using multiple parsers, to satisfy all of their technical and time constraints.

Before using Resource Traceability
	Add Resource Traceability properties. to the polarion.properties file for either a Single Server or Cluster setup.
	Configure Repositories. (Supports SVN, GIT or Polarion's default repository.)
	Add Linked Resources to Work Items. Add <extension id="linkedResources" label="Linked Resources"/> to each Work Item type that Resource Traceability will be used with.
	Configure resource-traceability.xml. Configure Where, When and How Resource Traceability parses data to Work Items.
	Check logs for errors. For Administrators: Check the new log4j-rt log regularly for parsing results and errors.
	Learn the source code syntax. For Developers: The source code syntax used to link where they implemented a source code change to the Work Item that requested it.

Warning:

If planning to use Resource Traceability with large or multiple repositories, increase Polarion’s memory allocation.