It seems as if phpBugTracker is already installed in this database and with this table prefix.

You can do one of the following:

1. Go back to the previous screen and choose another database or another table prefix.
2. Force an install in this database and with this table prefix.
3. Save a config file with the submitted options and upgrade your old database.

1. Choose another database or table prefix

If you wish to have a look at the newest version of phpBugTracker and try it out in a safe environment while deciding whether it is stable enough for your needs you can better choose another database or table prefix. Keeping the new and old versions of phpBugTracker in separate databases or separated by different table prefixes you can run both versions without any interference. But there will also be no interaction between the two versions. To be able to work with your old bugs in the new version your old database will have to be upgraded one day.

2. Force an install

This is usually a bad choice. If you have tried to install phpBugTracker but failed and now think that the problem is solved a forced install might be what you want. Another possibility would be to instead remove the half-installed database or tables to allow a normal install.

3. Save options and Upgrade

If phpBugTracker is already installed upgrading the database is almost always the right thing to do. This will let you use the new version of phpBugTracker with your old bugs.

Notice: Your database will be modified during the upgrade. There is no guarantee that an earlier version of phpBugTracker can still be used after an upgrade. We hope that the upgrade will go smooth and that the new version is stable enough for you to use. But you are warned: There is no easy way back. Please backup your database before continuing.