Hide Forgot
Description of problem: From time to time, it happens that we want to get rid of some testcase. The typical use case is when a testcase was mistakenly imported multiple times. While deleting testcases is not supported, and will never be, it'd be nice to have the possibility at least to pretend that a case has been deleted. The testcase having the status "DELETED" would - be still accessible by directly entering the URL containing case number, for archive purposes - appear only in runs that included the case before it was set to DELETED, for archive purposes (note that including a case in DELETED status would not be possible) - not appear in any testplans - not appear in any search results, unless the search was explicitly set to include DELETED status, i.e. searching cases with unspecified (any) status would NOT show DELETED cases
The test case can be disabled :Change status to 'DISABLED' The disabled test case couldn't be used to create test run. The DELETED status would be duplicated. (In reply to comment #0) > Description of problem: > From time to time, it happens that we want to get rid of some testcase. > > The typical use case is when a testcase was mistakenly imported multiple times. > > While deleting testcases is not supported, and will never be, it'd be nice to > have the possibility at least to pretend that a case has been deleted. > > The testcase having the status "DELETED" would > > - be still accessible by directly entering the URL containing case number, for > archive purposes > > - appear only in runs that included the case before it was set to DELETED, for > archive purposes (note that including a case in DELETED status would not be > possible) > > - not appear in any testplans > > - not appear in any search results, unless the search was explicitly set to > include DELETED status, i.e. searching cases with unspecified (any) status > would NOT show DELETED cases
changing status to "DISABLED" is not enough for us, at least not with the current implementation see for example here: https://tcms.engineering.redhat.com/plan/4371/#reviewcases all those cases listed should not be there, they are duplicates created by wrong imports or so - they are not "to be reviewed", but to be discarded completely there are two problems here: 1) the script used to create this plan should have not imported the cases into the plan in the first place but the script has no crystall ball to be able to know whether these cases are DISABLED because of the abovementioned reason (that they were created by mistake and should never be used) or they are DISABLED for any other reason and they may be enabled (i.e. switched to CONFIRMED, PROPOSED or NEED_UPDATE) again, i.e. whether they should or should not be included in the plan 2) once those cases are in some plan ... switching to the proposed DELETED status should remove them from all plans - of course, this could be achieved by removing the cases from plans manually, but the point is not just to remove them but also prevent them from being added again (i.e. "not appear in any testplans", as written above)
+1. DISABLE is the only state that express that a test-case has reached the end of life. because of this it is overloaded and used for many different use-cases: - disabled - deleted - obsoleted - duplicate - ... There are sometimes slight, sometimes big differences between those and one 'DISABLED' state can't satisfy them all.
TCMS doesn't support DELETE cases in UI, if you really has some wrong cases needed delete. Please send a list to tcms-dev-list, admin can help to delete them. Then these cases will dispeared for ever in the db.