Closed & Archived projects
- Active projects behave just as now the do. They are readable/writable.
- Closed projects are read-only. Nothing related to the closed project could be altered / deleted / added. It may be referred though (issues, wikis, files, documents etc)
- Archived projects are completely invisible as they are now.
I've read about similar proposal in ChilliProject : , 
Updated by Fernando Hartmann over 11 years ago
This would be very useful for us.
We create a lot of sub projects and want them available tho future read, but what to remove them from some search queries.
It would be very interesting to have filters to choose if the user want to "see" the closes project too, like we do nowadays with issues.
Please put this issue at least on Candidate for next minor release !
Updated by Nick Nguyen over 11 years ago
This would also allow time logged to closed projects to appear on time reports. Currently time logged to projects 'disappears' when a project gets Archived. trying to review time logs for the year becomes an issue because of this, and I have to create queries to pull them directly out of the database.
Updated by Bernhard Furtmueller about 11 years ago
Updated by Brandon Liles about 11 years ago
Updated by Brian Heasley about 11 years ago
Archiving a project as it stands is pretty useless (for us).
Updated by Eric Le Gallais about 11 years ago
This would be useful to us too.
Updated by R. Steve McKown about 11 years ago
For us, daily use of Redmine centers around operations with the current set of active projects. For these use cases, including closed projects adds a large amount of 'noise' to result sets.
Since we have dozens of large, closed projects, the knowledge they represent is exceptionally valuable. It's not practical, at least for us, to archive these projects and lose the ability to search, etc.
There's lots of places in redmine where the project list, either implicitly or explicitly, is referenced. Adding this feature might be fairly involved. But perhaps there is a way to move down the road to a complete solution with a useful first step. Perhaps, from a user usage perspective:
- Each project gets a boolean attribute, Active (or Closed).
- Extend the project drop-down on the page header. It shows active projects and a 'more' option. The more option brings up some form of HTML object allowing selection of a project from the full list.
- Extend the project drop-down on the search page, adding "Active Projects" and keeping, of course, "All Projects".
Updated by Jose de Leon almost 11 years ago
Along this line of setting project status, I think there should also be a "Visibility" ACL of some sort. That is, administrator can specify where "Archived" projects are visible, or where "Closed" projects are visible.
For example, if I close a project, then perhaps I don't want it to show on the Overview tab, but I still want it to show in the projects listing. For archived projects, I might want it to only show to administrators and nobody else, but Managers would have ability to archive a project, etc, but once archived, they can't view them or do anything to them.
Updated by Andriy Lesyuk almost 11 years ago
Accidentally came across this issue...
I think my plugin Role Shift can help here: You need to create a shift role with all write/modify permissions disabled and shift original roles with this role. You can also add "Closed" boolean custom field to show that a project is closed.
Hope this helps...
Updated by @ go2null over 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Implemented in v2.1.0 as Feature #3640.
Closed projects: a new permission is added to let project members close/reopen projects. Unlike archived projects, closed projects are still visible but the project and all its data (issues, wiki...) is read-only.
Updated by Jean-Philippe Lang over 10 years ago
- Status changed from Resolved to Closed
- Resolution set to Duplicate