I've got a draft email to the powers that be suggesting something similar. It's a work in progress while I work out the reasons for keeping them. I suppose one reason would be that someone could be using a module, unaware that it has been deleted. Bugs, patches and coversations submittied via RT would still be available for reference. As yet this is the only sensible reason I can think of for keeping them. Thanks for your input.

Update: Raised as a meditation.

NaP marto, pleased (and surprised) to have been of some use/help :-)

As a CM practitioner, I would suggest that, in addition to your meditation, an extra 'final' lifecycle state is introduced that clearly and unambiguously identifies such tickets as to be raised but unaddressable e.g. 'will not fix - obsolete module' or similar ?

A user level that continues to overstate my experience :-))

in short :) backpan, thats why :)

Hmm, I don't believe that's a valid rationale - the suggestion is merely to modify the disposition of, c/w remove, the ticket in order to improve the status reporting and indeed, accounting.

Update:

Reworded - s/state/disposition/

A user level that continues to overstate my experience :-))