Sergiu Dumitriu wrote: Oh, didn't notice that this is about the Jira project... Then I'm -1, since Jira should always be a point of reference, even for historical issues. SVN has its history internally, so we can always see past commits, and those commits will refer to Jira issues, but since Jira doesn't have a real history, there will be no way to see all the details for deleted issues. An alternative would be to move the issues to the core project, but it's not a good one, IMO, since: - it involves a lot of work to determine the correct version mapping between the two projects - release schedules might not overlap entirely, since we released tools both for increasing 1.x milestones and out-of-order 1.(x-1).z bugfixes - I don't know how Jira works, so if we do move issues and then delete the project, I'm not sure redirects will continue to work. So, I propose to leave the project in place, and remove permissions so that nobody can create new issues in it. I think that there is a way to display a custom header for that project, to let people know it is deprecated. -- Sergiu Dumitriu http://purl.org/net/sergiu/