R4J Suspect Analysis

[Tcheunou Tchokomeni Charlie]

I want to identify the issues linked to a specific requirement(s) during a change request

R4J Suspect Analysis does not cover the requirements we have for an impact analysis

The restrictions of the suspect analysis are:

 * no baseline based comparison

Someone maybe an idea on how to perform a Suspect analysis (Suspect Report) base on baseline Comparaison ? Or advice abaout a addon for this ?

[Bernhard Doleschel]

Disclaimer: I am a employee of the vendor, Ease Solutions.

Hello Charlie,

thanks for the question. As we already in close contact via our service desk, we will further inform you about the progress there.

The suspect analyses is a monitoring concept, which is triggered by changes on current revision of a issue. If the change match the suspect configuration, a notification is triggered to respective issue owners. The suspect report provides an overview on all detected cases.

The analysis you mention above is a view into the future like an if-then analysis. You can resolve this by the coverage analyzes: From an issues (to be changed) you get all linked issues (next and further traces) which may affected by such a change. Currently we do not include baseline data in our coverage view.

Best regards, Bernhard