It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×10,908
×7,383
×5,997
×1,211
×750
×482
×139

question asked: Apr 29 '20, 3:59 a.m.
question was seen: 1,693 times
last updated: Apr 29 '20, 4:06 a.m.

Related questions

FAQ - How this Forum works

Do you know why blocking Status is not set correctly in an Opt In environment when the preference When a new test execution record is created?

0
Natarajan Thirumeni (298●7●31) | asked Apr 29 '20, 3:59 a.m.
Blocking Status is not set correctly in an Opt In (GC / CM) environment when the preference When a new test execution record is created, make the development items from the associated test case blocking defects is set. When we ran a test the TCER (Test Case Execution Record) should be marked as blocked but its not. How do we fix this issue?

One answer

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Natarajan Thirumeni (298●7●31) | answered Apr 29 '20, 4:06 a.m.

This issue was caused by the code to handle a project property (required to enable this feature) did not support CM-enabled projects, which links are stored in LDX. For GC / CM enabled project areas - its a known defect in v6.0.6.1 and earlier. Please see APAR PH18154. The defect has been fixed in v7.0 and beyond.


Due to complexity of the code change its too risky to back-port a fix into v6061. Please use v7.0 instead. 

Please note: The problem do not occur (that is, TCER is marked as blocked as expected) in non-GC projects.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.