Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

R4J Suspect Analysis

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 ?



1 comment

Bernhard Doleschel
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 11, 2020

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


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events