Customizing Fast BugTrack
We don't recommend this color scheme... But here are some examples of the customization possible:
Customizing Built-in Fields
Disabling the Project Management Fields
The fields "Requested Due Date", "Actual Completion Date", "Estimated Hours", "Actual Hours", "Percent Complete", and "Parent" can be disabled if you are not planning on using these fields. To do this, Select "Administration Menu", "Server" and check "Disable Project Management Fields". This change will take effect when users next log into the system. Stopping and restarting the server will force all users to log in again.
Other Built-in Fields
The names of the other fields may be changed for your own purpose. For example if you are working on a web-based application, and are not using the "Environment" field, but would like to rename it to "Browser", and have the user choose the browser that they are using, you would use the "Customize Strings" functionality. Select "Administration Menu", "Advanced: Customize Strings". Almost all of the strings within Fast BugTrack appear here.
You will see three columns, the first contains a link "Edit" (and might contain a second link "Reset" if a string has been changed). The second column contains the tag name. These are the tags used within Fast BugTrack's templates. The third column contains the current value of the tag. All of the field names have the tag "sColumn<FieldName>", where FieldName is the name of the field. In our example above, we would press "Edit" next to "sColumnEnvironment". Enter a new string in the textfield present and press "submit". The change will take place immediately, even for users that are currently logged in.
Special strings include "sHead", "sFoot", and "sBottom". These strings appear on every page. The sHead tag appears in the <HEAD> section of an html template. The sBottom tag appears below the html for the menu, and above everything else on a template. The sFoot tag appears at the bottom of an html page, and could be used to close any tags opened in the sBottom tag.
Adding Custom Fields
Custom fields may be added by selecting "Administration Menu", "Field". Any
existing custom fields will be displayed in a list at the top of the page.
Type the field name, as you would like it to appear on the new, view, and
modify screens. Select the field type, where "String" is a string (such
as the existing Version field), "TextArea" is a larger box (such as the
existing Description field), and "List" is a dropdown list (such as the
environment field). Enter information into the box beside the list will
populate data in your dropdown list (one entry per line). Checking
the "Field History" box will keep a record of each change to this information
(such as the status and assigned to fields) - this is a less efficient way
to store data, so only use this if you really require a history for this field.
The sort order impacts the order that the custom fields will be displayed.
Custom fields will always follow all of the existing fields except historical
fields will always appear second last (above the description text area).
Changing the logo - Registered Versions Only
To switch our logo to yours:
- Place your .gif or .jpg in the c:\Program files\FastBugTrack directory.
- From the administration menu, Customize Strings, the first entry is "rLogo".
- Press edit... In the textbox, type the filename of the new logo... Your change
should take effect immediately...
Using Style Sheets to Customize the Look and Feel
Customizing the look and feel is an advanced topic. You must be familiar with html and style sheets in order to take advantage of this functionality. Many tutorials about style sheets exist on the Internet.
Fast BugTrack uses style sheets to define the look and feel. You can view the default style sheet by going to the Fast BugTrack server URL, and adding "main.css" (Ex: http://localhost:10000/main.css). Depending on your browser, you may be prompted for a program to view the file with - If so, choose a text editor such as notepad on a Windows system.
A good way to start customizing the look and feel is to save this template, and use it as a starting point. Save it in your Fast BugTrack directory. The filename must end in ".css" (and you will want to call it something other than "main.css"). Stop and restart the Fast BugTrack server. Select "Administration Menu", "Server", and you should see your css file in the "Stylesheet to use" dropdown menu. Select your stylesheet name, and press "Change Settings". This change will take effect when you next log in, so you will likely want to logout and back in. Changes to your stylesheet should now be reflected immediately in the pages delivered by Fast BugTrack.
|
