Redmine

Would be also necessary to "unclose" the closed projects of course... When needed...

+1 It'd be very useful indeed...

Eric

couldn't you get the same effect by just turning off edit permissions ? in our case we use groups and just demote the role of the group to 'reader' or some such on that project. Not sure if that has the effect you are looking for on time recording though.

Of course there is a lot of work around but with such solutions the work to reach the goal is rather heavy...
Redmine is very powerfull concerning permissions.
You can, project by project assign different roles to different users.
But with the solution you propose... Imagine the work to realize that !
You have to create a role developper and also a developper read only, a project manager and a project manager read only etc etc and after, each time you want to close a project, you have to change all the access you created. A lot of work for a basic stuf.

I add some precision to my suggestion in cas of not clear enough.
The goal is to close a project but leaving Read access to all defined members.

No more Issue creation, no more time logging, no more new comments, no more new documents etc...

Best regards.

I just want to cancel one project then I found this problem.
A project can be turn to "Closed" and all the write access will be disabled no need to modify permissions one by one, and the project name will be display in "GRAY" or add a tag "CLOSED". I think this is what I want. Please add this feature in 1.0.0.

Thanks.

Would it be a big deal to add such a "CLOSED" project status?

Here, we're dealing with many projects over time. We don't want to archive older ones because they contain all our past experience and we must have access to this knowledge.

Otoh, these projects are (contractually) finished and we would like to clearly mark them as CLOSED, and make them read-only. This would be a Project Management phase. Not the same as manually removing write permission for everybody in an "active" project...

Thanks, Eric

• Configurable status. We have several: incubating, open and closed
• Assigned to:person in charge
• Category: This would be grate to associate each to the department in charge
• % done
• Estimated time
• ... And on and on

In fact, for me, projects are just some sort of superissues. Providing them with the same characteristics of an issue would help us manage our project portfolio just as we do with our issues portfolio within a project.

I´m very interested in the functionality just mentioned by Pedro.

Project may be treated in some cases as issues.

Agree! +1

+1

+1 as I will need it as soon as my 4 student projects end september 2011

This is pretty annoying for us as well, there is a lot of knowledge in the old tickets that is not available simply because redmine is blocking access to the archived projects tickets. It seems silly that the search is incapable of finding archived tickets. Either make archived tickets searchable/viewable or add a "Closed" Status.

+1 I use Redmine to manage all our student and research projects - currently there are over 300 and changing role permissions takes ages with so many projects.

How can it be that Redmine team find fixing code for Internet Explorer 6 support more important than to add a useful feature for managing projects...
Here we have many projects and Redmine becomes unpractical. Come on, giving a closed status to a project isn't that unusual in PM...

Watched.

My key requirement is to have the knowledge contained in an archived project be searchable.

+1

Similar to this request: #8681