The traces should appear in the order they were created in Caliber client.
However DocFactory has introduced a new command called $sort_traces
Please see the CaliberRM 10.1 readme notes below:
This command is primarily use to sort traces within DocFactory. The new command follows the same syntax convention with $sort.
Following identifiers can be passed to $sort_traces as parameters: trace_regtag, trace_name, trace_suspect, trace_teststatus, trace_directimplied, trace_direction, trace_project, trace_type, trace_tag, trace_description, trace_status, trace_priority, trace_version, trace_owner, trace_created_on, and trace_created_by.
Thank you for the response, knowing about the $sort_traces will be useful.
However, I am not sure that this allows me to acheive what I need.
Our requirements consist of use cases and functional requirements that support the use case. Each of these is a separate requirement type within CaliberRM.
The functional requirements are traced from the use case(s) that they support.
I am trying to find an easy way of producing a document that contains a use case followed by the functional requirements that support the use case.
Within CaliberRM the functional requirements appear in the hierarchy in a logical order so that they make sense when reading down the hierarchy. However, the functional requirements were not necessarily authored in the order in which they appear, nor were the traces to the use case(s) they support necessarily created in order.
Therefore, what I need is the ability to sort traced requirements into hierarchy order and I can't see any of the trace attributes above give the capability to do this.
Can you think of a way to output traced requirements in the sequence that they appear within the project hierarchy?