Configuration of Alcea Fast IssueTrack is done by running it immediately after it has been installed. Alcea Fast IssueTrack will start, and then with your web browser go to the appropriate webpage and start configuring!

• Start Alcea Fast IssueTrack in the location that you installed it.
• Point your web browser to the appropriate URL. If you are running your web browser on the same machine that you are running Fast IssueTrack, you can probably use http://127.0.0.1:10000/ or http://localhost:10000/. If you are running a web browser on a different machine, you will want to use the name of the machine where Fast IssueTrack is installed, on port 10000. If you are not sure what you should be using, check with your network administrator.
• You will be prompted for a port to run Fast IssueTrack on once it is configured. The default is port 10000. If you are not sure, use the default, however you may want to use port 8080, or port 8888. Be sure to choose a port that is not being used by another piece of software (such as another web server). If you are installing Fast IssueTrack on a Unix machine, you must be running Fast IssueTrack as root to install it on a port below 1024.
• If you would like to enable email functionality, enter a valid SMTP Server. A SMTP server is the computer that is used on your network to send email. If you are not sure what this should be set to, you can check the settings on an existing email program, and if you are still not sure, check with your network administrator.
• If you are enabling email functionality, you can set the "From" field that Fast IssueTrack will use for sending email. Your SMTP server might set some restrictions on what this value can be (for example it might have to be a real email address for your SMTP server). You may want to use an email address dedicated for Fast IssueTrack, or you may want to use an existing email address (such as your own).
• Click "Submit"
• Step 2 is to create users for Fast IssueTrack. You will want to create a user for each real user (programmer, tester, manager) of the issue tracking system. You do not need to create all of your users at this point. However you must create an administrator (probably yourself). The administrator can add and remove users while Fast IssueTrack is running during normal everyday use. If you have enabled email functionality, you can include an email address for each user that you create. If a user does not want to be notified when a issue has been assigned to them, this field should be blank. This can be changed after the server is up and running.

  After you have created a user at least for yourself (with administrator privileges), click "Next Step (Create Projects)".

• Step 3 is to create Projects for Fast IssueTrack. Projects are used to keep track of major software projects. You must create at least one Project even if you do not plan on using the Project field. After creating at least one project, click "Next Step (Create Project Areas)".
• Step 4 is to create Project Areas. These are areas within a project, such as "client", "server", "database", or "installer". You must create at least one Project Area even if you do not plan on using the Project Area field. After creating at least one Project Area, click "Next Step (Create Environments).
• Step 5 is used to create Environments against which issues might be reported. Environments might include "Production", "System Integration", "Development", or "Bob's PC". You must create at least one Environment even if you do not plan on using the Environment field. After creating at least one Environment, click "Last Step (Final Instructions)".
• Step 6 is not really a step, it outlines some additional information for Fast IssueTrack. The instance of Fast IssueTrack will now exit. The next time you start it, it will be in issue tracking mode. Start Fast IssueTrack again, and login with your user id and password to start using Fast IssueTrack.

• If you would like to re-run the installation process, delete the file called "server.cfg" created in the Fast IssueTrack directory. When this file exists, Fast IssueTrack runs in issue tracking mode - but when it is not found, Fast IssueTrack runs in installation mode.
• All of the items that are configured at installation time, can also be configured in issue tracking mode. See "Administering Fast IssueTrack" for details.