As a suggestion for future users, we have set up a special Test Project, where we can test
out basic settings, get users used to using Eventum, etc. That way, we can delete that
project or not give access when we are ready for production use and it doesn't require
deleting out customizations from other projects. I've also set up a DB for reporting
issues with Eventum itself, so I can check back on the mailing list to see if it's a
problem everyone is having and if it's been fixed yet.
And moving the DB to the new server works fine, we've just finished doing a test run of
that and didn't have problems. Just make sure you've pointed it towards the right
database so you don't accidentally populate something else instead. Not that I did that
or anything, of course. ;-)
Tamara Harpster
--- On Tue 06/14, Joao Prado Maia < jpm@stripped > wrote:
From: Joao Prado Maia [mailto: jpm@stripped]
To: eventum-users@stripped
Date: Tue, 14 Jun 2005 14:18:34 -0500
Subject: RE: we are moving eventum to production
Joe, <br><br>> what a great product!<br>> <br><br>I'm
glad you like Eventum - spread the word! :)<br><br><br>> this brings
a couple of questions to mind:<br>> - can we clear the issue tables and keep
the customization <br>> we've created?<br>> - is there another method
that will have the same effect as <br>> eliminating<br>> issue data but
allow us to retain our customization?<br>> <br><br>What type of
customization are you referring to? If it is just a matter<br>of custom statuses,
priorities and categories, sure, you should be safe<br>removing everything from the
issue table.<br><br>--Joao<br><br><br>-- <br>Eventum
Users Mailing List<br>For list archives:
http://lists.mysql.com/eventum-users<br>To unsubscribe:
http://lists.mysql.com/eventum-users?unsub=1
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
