Brett,

When generating Export file, HAR validator stated " Negative time is not allowed:" for about 5 different lines.  Is this normal?

Stuart

Brett,

I still get "No Items Found".  I created a use case module based on our standard use case template which already had sample requirements.  I created a collection and included new module.  I created a new sandbox test plan and added collection to requirements collection.  When selecting "View Aa" "Coverage", I get "No Items Found".  Let me know what steps I need to take with Firebug if need be.

Brett,

Firstly, thanks for looking into this.  I do have "Traceability" in the "View As" dropdown" for test plans.  When doing this, it highlighted another aspect of my issue.  The "View As" "Coverage" in test cases basically worked in the past.  On other test plans when I added a requirements collection (our collections are mostly use case modules), it would display the actual list of use cases rather than a link to the requirement collection.  This can be seen more clearly when using the "View" "Traceabilty" when browsing test plans.  In the ones where "View As" "Coverage" displays something, it's where the use cases are displayed rather than when just a requirements collection link is displayed:
Example:
"Product X Release Test Plan"      "12345: Requirements Collection Name"
VS.
"Product Y Release Test Plan"        "(1), (2), (3), (4), (5),...." where each one of these numbers is a link to a use case within a requirements collections

Brett,

Here's an interesting update on our issue that we are still having but now seem closer to what may be wrong with back links etc. A portion of our problem appeared to be with browser caching (using Firefox...issue was discovered by switching to Chrome).  So now some items show up for "View As" > "Coverage" under "Requirements Collections Links".  What is showing up are file types in the collection identified as artifact type "Sketch".  Isn't the "Coverage" only suppose to drill into the "Use Case" artifact types associated with the collection and retrieve only those artifacts that are identified as "Requirement"?  Otherwise, we will never get our traceability to work correctly if not back linked to the requirements.  The "Collections" in this instance has:  1 module of type "Requirements", 4 modules of type "Requirement Specification", 2 files of type "Sketch", 14 modules of type "Use Case".  All are stored under project "root" folder.

Brett,

Yet even more discoveries and final root problem.  By looking at the use cases that were correctly linked through requirements collection link in test plan, each use case module had a "Validated By" link that was created when the collections module was added to the test plan. So the actual current problem is that when now when we add a collection, the system is not creating the "Validated By" back links from the use case modules associated with the the select requirements collection.  If these are manually added from the use case side, then the use case shows up.  However, we obviously would like this to work correctly from the test plan perspective so that we do not have to manually add the links from the use case side.