Susanne Chau wrote:
> Hi Watson,
> Thanks for your answer. In my case I would like to keep all issues in
> the DB for later check-ups if needed.
> Main reason for wanting to archive old projects was because all
> different projects have not been very aligned when it comes to the
> customized fields. This make it difficult for us to move issues between
> the projects. We do know there are some issues that still could be
> useful, but to start from scratch I decided to archive the old ones and
> create new with same customized fields..BUT if we find out later on that
> there are some issues we would like to check again, I would like to be
> able to do this.
> So is the only solution like this or is there anyone else who has better
> 1. Mark project as archived
> 2. Unmark all users with access to the old projects to avoid mistakes
> reporting issues to the old ones.
What features would you like to see for "archived projects"? What do you want users to be
able to due and not due? I have had people ask for this before but don't have a clear
picture of everything they want.
Bryan Alsdorf, Lead Web Developer
Monty Program, AB. http://askmonty.org