how to stop the parent defect severity change when being marked as dup of the child defect?
When a defect is marked to DUP of another defect, RTC automatically change the severity of children defect onto parent's defect severity. For example, defect A has severity of S3 and defect B has severity of S2. Developer analyzed the issue and believe defect A is the same problem with defect B so he marked defect A as DUP of defect B. RTC automatically changed defect B (parent of the DUP) severity to S3 to match the defect A severity.
This is a problem because a children defect should never update the severity of the parent defect.
RTC Version 4.0.7
This is a problem because a children defect should never update the severity of the parent defect.
RTC Version 4.0.7
One answer
Hi, Aparna
I don't know if we should consider "duplicate of" as a parent-child link type. To me they should be the same level.
Yes, I do see the similar behavior in my local test, but it is not the same as what you described.
If defect A is severity 3 and defect B is severity 2(higher), if defect A is set as 'duplicate of' defect B, defect A will
be at resolved state and severity of defect B will not change because S2 is higher than S3(of the resolved duplicate defect).
If defect B is set as 'duplicate of' defect A, then defect B is will be at resolved state, severity of defect A will change to S2.
Although I can't find any explanation of this behavior anywhere, it does make sense to me that for the two duplicated defects, the higher severity should take precedence. I don't see any way to workaround the issue unless the user manually update the severity after change.
If this behavior can be clearly documented, that would be helpful. In that sense, you may comment in this Infocenter to add more explanation on 'duplicate of/duplicate by' link:
http://www-01.ibm.com/support/knowledgecenter/SSYMRC_4.0.7/com.ibm.team.workitem.doc/topics/t_triaging_work_items_web.html?lang=en
I don't know if we should consider "duplicate of" as a parent-child link type. To me they should be the same level.
Yes, I do see the similar behavior in my local test, but it is not the same as what you described.
If defect A is severity 3 and defect B is severity 2(higher), if defect A is set as 'duplicate of' defect B, defect A will
be at resolved state and severity of defect B will not change because S2 is higher than S3(of the resolved duplicate defect).
If defect B is set as 'duplicate of' defect A, then defect B is will be at resolved state, severity of defect A will change to S2.
Although I can't find any explanation of this behavior anywhere, it does make sense to me that for the two duplicated defects, the higher severity should take precedence. I don't see any way to workaround the issue unless the user manually update the severity after change.
If this behavior can be clearly documented, that would be helpful. In that sense, you may comment in this Infocenter to add more explanation on 'duplicate of/duplicate by' link:
http://www-01.ibm.com/support/knowledgecenter/SSYMRC_4.0.7/com.ibm.team.workitem.doc/topics/t_triaging_work_items_web.html?lang=en
Comments
Comments
Donald Nong
Mar 01 '16, 9:12 p.m.