id	summary	reporter	owner	description	type	status	priority	component	severity	resolution	keywords	cc	release
7945	Bad ticket number in 'blocks' or 'blocked by' prevents viewing of ticket.	anonymous	rjollos	While noodling around with TracXMLRPC, I discovered that if ticket X has populated fields 'blocks' and/or 'blocked by', and the tickets referred to in those fields doesn't exist, then when I attempt to view ticket X, trac reports\r\n{{{\r\n  Error: Invalid ticket number\r\n\r\n  Ticket 93 does not exist.\r\n}}}\r\nWhere 93, in this case, was in the blocks field. Ticket X is now completely unavailable, even to TRAC_ADMIN, unless you poke around in the db and remove the offending ticket numbers.\r\n\r\nWould it be a better idea if !MasterTickets reported that the referred tickets are invalid - perhaps by unWiki'ing the ticket numbers, or striking them through - but allow you to view or edit ticket X?\r\n	defect	closed	low	MasterTicketsPlugin	normal	worksforme			0.12