Bug 698206

Summary:	Remove case-bug removes case-run-bug
Product:	[Other] TCMS	Reporter:	Petr Šplíchal <psplicha>
Component:	Application	Assignee:	Yang Ren <ryang>
Status:	ASSIGNED ---	QA Contact:	Nobody <nobody>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.0	CC:	azelinka, junzhang, jzhao, ohudlick, ryang, vchen
Target Milestone:	---
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	593666

Description Petr Šplíchal 2011-04-20 12:41:24 UTC

Description of problem:

Removing a bug related to a test case (added under the test case
"bugs" tab) cause the same bug added from a specific case run to
be removed as well.

Version-Release number of selected component (if applicable):
Nitrate 3.3-4

Steps to Reproduce:
1. add bug 1234 under test case -> bugs
2. add bug 1233 under case run -> add bug
3. got to case -> bugs and remove bug 1234
  
Actual results:
Both instances of the bug 1234 removed.

Expected results:
Only the case-base instance removed.

Comment 1 Petr Šplíchal 2011-07-27 05:57:08 UTC

This is quite dangerous issue as it can cause relevant bug
information to be completely lost. Could we get this fixed soon?

Comment 2 Jin Zhao 2011-07-27 07:47:36 UTC

Modify step2:
2. add bug 1233 under case run -> add bug
Should be add bug 1234 under case run -> add bug

Comment 3 Chaobin Tang 2011-09-30 07:54:20 UTC

There is a design drawback behind the scene. The connection between a bug and a caserun is somehow translated into that between a bug and a case, consequently, adding/removing bug of a caserun will literally add/remove the bug of the case.

Consideration on re-implementation of this functionality is required, and that takes further effort.

Comment 4 Ales Zelinka 2011-09-30 14:16:15 UTC

What about reimplementing the case-run-bug removal so that: case-run-bug is removed, the same bug is re-added as case-bug. 

And change the wording on the case-run-bug removal dialogue to make this clear to the user (call it unlink or something...).

Or offer two action on case-run-bugs: unlink from run (remove case-run-bug, leave case-bug) or remove (remove case-run-bug, no case-bug remains either).

The one drawback I see with this add-after-removal approach is that it will be visible in case changelog and might be confusing to users. Worth it though.