It's all about the answers!

Ask a question

How to remove the Wrong links appearing in the JRS reports?


Dhanya Saseendran (8821121) | asked Jan 28 '16, 2:27 a.m.
Hi,
In the JRS report there are old links appearing.
I had moved one of the Project Detail work item to a parent Account work item - Global R&CM
So in the below picture, SUBK_DA Implementation is actually the child of Global R&CM.
And the previous parent was IBM ACCOUNT.


The traceability link used is


The version of JRS being used is 5.0.2
Please help me to understand why the wrong information on the parent is coming in JRS.
What is the solution to correct this?
Thanks
Dhanya

Accepted answer


permanent link
Darren Coffin (1823) | answered Jan 28 '16, 9:15 a.m.
JAZZ DEVELOPER
Hi Dhanya,

What iFix level is your 5.0.2 JRS?  There was a fix that went into 5.0.2 iFix 009 which should fix this issue.  See [RTC 5.0.2iFix009] WI: 360995: Ghost links appearing in traceability report (368403)
Dhanya Saseendran selected this answer as the correct answer

Comments
Darren Coffin commented Jan 28 '16, 9:23 a.m.
JAZZ DEVELOPER

Correction, this problem  has only been partially fixed in 5.0.2.  It has been fixed so that running the DCC jobs will properly set the ghost link as archived/deleted in the data warehouse.  There is another fix coming soon (next iFix) which will make JRS properly filter out the archived links.


Dhanya Saseendran commented Jan 28 '16, 10:07 a.m.

Hi Darren,

we are soon getting upgraded to 6.0.1 hope this will resolve the issue?

Thanks
Dhanya


Darren Coffin commented Jan 28 '16, 10:34 a.m.
JAZZ DEVELOPER

Hi Dhanya,

Yes, the issue is resolved in version 6.0.1 as well.


Rafik Jaouani commented Jan 29 '16, 5:00 p.m.
JAZZ DEVELOPER

Hi Dhanya,
After upgrading to 6.0.1, please run a normal ETL in DCC and make sure it passes.
Then make sure you push back the delta time of the affected server in DCC to the date when you started using 5.0.2. This will fix the past link data in the data warehouse.

One other answer



permanent link
leo chung (112) | answered Jun 07 '18, 2:33 p.m.

Hi Darren/Rafik,


I'm running 6.0.4 ifix 4 and we are seeing this exact same issue.  has the bug resurfaced?

Thanks!

Your answer


Register or to post your answer.