ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Allow to close projects as opposed to archive them (Feature #315)

Added by Harald Frießnegger at 2011-04-05 09:32 am. Updated at 2011-04-08 10:11 am.

Status:Open Start date:2011-04-05
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:

Description

there should be a way to mark projects as done (so they do not appear in the list of a users current projects)

currently projects can be archived, but related tickets, bookings etc are not accessible any longer.

it would be much better if tickets could still be accessed (eg for developers to check how they solved a similar problem last year) but of course not reopened, etc (in case the project is archived)
archived projects could be listed in a separate view linked under "archived projects" in the /projects/ view.

i'm not sure if this would affect other parts fo the application.
neither i'm sure which category to pick below. I'd go for workflow if it was there.

if you've got any questions to this request i'll be happy to answer them ;-)

History

#2
Updated by Holger Just at 2011-04-05 10:48 am

Currently, archiving means that a project is not accessible at all anymore. So we need a new term for your proposal (or redefine the existing one). I propose to use "close" as opposed to archive.

For the implementation, we could at first disallow any writing permissions on a closed project. Additionally, closed projects must be clearly marked as closed everywhere (i.e. in issue views, wiki pages, ...)

  • Subject changed from Offer a way to archive projects to Allow to close projects as opposed to archive them

#3
Updated by Eric Davis at 2011-04-06 10:10 pm

I use a custom field on each project for this. It doesn't hide anything but helps me organize a bit.

Having a way to close or mark a project as read only would be useful (but might take a bit of work to mark all the "read" vs "write" parts).

#4
Updated by Harald Frießnegger at 2011-04-08 10:11 am

thanks for your feedback!

Holger Just wrote:

Currently, archiving means that a project is not accessible at all anymore. So we need a new term for your proposal (or redefine the existing one). I propose to use "close" as opposed to archive.

For the implementation, we could at first disallow any writing permissions on a closed project. Additionally, closed projects must be clearly marked as closed everywhere (i.e. in issue views, wiki pages, ...)

using the term close for this functionality sounds perfectly fine to me.

Eric Davis wrote:

I use a custom field on each project for this. It doesn't hide anything but helps me organize a bit.

"a bit"... exactly ;-)

Having a way to close or mark a project as read only would be useful (but might take a bit of work to mark all the "read" vs "write" parts).

as both of you stated, we'd first need to define which places need a change:

  • closing a project should only be possible when all tickets are closed
  • in closed projects adding/editing new items (tickets, wiki, news) must not be possible (we might consider to make this configurable, since it might make sense to correct documentation in the wiki of a closed project)
  • /projects should only list active ones. closed projects sould be accessible via a separate link
  • when viewing content of this project, we could display "this project is closed, you can't edit this item" in the statusbar

Also available in: Atom PDF