R David Murray added the comment: I misspoke. Looking at the edit screen again, the issue is the 'leave in/leave out' versus 'delete', which is indeed retire. The complicating factor is: what if you 'leave in' a public query that someone then retires? It is stuck on your visible list with no way to get rid of it, if you can't see retired issues.
I'm not sure what the best solution is. Maybe it is indeed to just hide it in both the visible and edit list if it is retired, but that would mean a resurrected retired query could suddenly show back up some day. I think the problem at the moment is that you don't see retired queries in the edit list, so you can't make them not visible. Showing retired queries that are 'leave in' might be a sufficient solution. It certainly would be nice if 'delete' also removed the query from being visible, but that would solve the problem of a visible query owned by someone else and retired. _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue598> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss Code of Conduct: https://www.python.org/psf/codeofconduct/
