Is it possible to write a report that shows an item's content from a past state but its "confirmed by" relationship from today? (Javascript)

[mkocur]

Hey Community:

a possible use case is as follows:

Your manager wants to get an overview of the progress in the last month. Thus you want to depict the progress by using a report.

This report should show the items with their content from the past but their "confirmed by" links from today.

If you run a report on the items in the past (to obtain the Requirement's original content) the report would show that no tests ( Confirmed by relationships ) have been executed til now. This is due to the fact that the Requirements were not tested at that moment in the past (certain Label). That's why I want the Confirmed by relationship from now (today) because some requirements have been tested over the last month (Confirmed by relationships exist now). By doing that it's possible to show which and how many requirements have been tested over the last period.

If you run a report on the items from today, you receive the current item's content (Requirement's content). Probably these contents are different from the original ones' because another divison is working on these requirements and developping them meanwhile.  The report would show different requirements and more important than that, no executed tests. On the one hand the test cases refer to the same ID, but when the item's content has changed over the last period the test is automatically in "execution mode" (even if it's passed or failed in a past state, actually).

In a nutshell: Is it possible to write a report that shows an item's content from a past state but its "confirmed by" relationship from today?

Best regards

Martin

[VolkerEckardt]

Hi Martin,

you are spotting a very interesting point: the time difference between test execution and possible changes of requirements.

The short answer is: a report will always respect "as of" that you provide during report execution, and this will affect all data.

Having some data as of now and some other in the same item as of another older date is not the idea of "data integrity" in Integrity.

Formally speaking: what you need to do is branching your requirement document to get a stable copy, and then execute the testing based on this requirement copy only.

The downside includes:

- tracing will have to be brought over by "trace propagation" - existing traces will have to be copied to the new requirement doc ...

- the branched document will have new requirement IDs

- the branched document will double the number of requirements in the current project.

Right now, I am discussing with another client how we can utilize document versioning to limit the influence of these formal issues, but the decision to go with that is not made.

Perhaps someone else has for us a good approach and is willing to share with us?

Volker

(Hint: I have written a Custom Gateway export (Word and/or PDF) which will exactly do what you are asking for, but this is Gateway, not an Integrity Report)