REPOST!!! Release Assembly - TC Cockpit Bug Race Cost and Fees Part 1

Project Overview

Right now we don't handle fees for project level bug races and contest bug races if the billing is fixed (instead of %) which is what need to be fixed in this series of assemblies.

Competition Task Overview

Requirements

To fix this, a possible solution involves the following changes:

1. Add two columns to tc_direct_project, bug fee and bug fee percentage.
2. Add a fake type here for bug race for fixed fee.
3. When associating a billing to a project, you should either set the % or fixed on tc_direct_project based on the setting. In most cases there will be only one billing per project so it would be straightforward to do this. But in some rare cases there can be multiple billing accounts for a project, in that case we will have to selelct anyone (probably the latest one) to use. So a possible implementation is: whenever a new billing account is assoicated to a project, we use the new one’s setting; If we remove a billing from a project, we either reset the settings to null if there's no billing associated with the project any more or we pick one from the remaining billing accounts associated with the project.

For this contest, the scope is to get the code updated and the queries updated to make sure the invoice report is correct. 

References

1. You can go to this page to set billing (fixed or %) using 'TC Accounting' role (you'll probably have to try this on VM, see "set_contest_fee.png" for reference).
2. You can associate billing when editing a project (https://www.topcoder.com/direct/editProject?formData.projectId=) or starting a new project (https://www.topcoder.com/direct/createNewProject.action). See "edit_project_associate_billing.png" and "start_project_associate_billing.png" for reference.
3. To see where invoice report is generated, refer to "invoice_report.png".

SVN

Please email support@topcoder.com to request access to direct trunk, please include the contest title/link and your user name in the email.

Direct Trunk: https://coder.topcoder.com/tcs/clients/cronos/applications/direct/trunk/
DB Trunk: https://coder.topcoder.com/internal/database/scripts/trunk

VM

VM specific information is found here: http://www.topcoder.com/wiki/display/docs/VM+Image+2.5.

Upon registration as a submitter or reviewer you will need to request a VM based on the new TopCoder Cockpit/Direct image. To request your image, please use the forum.

Before requesting your VM, you need to ensure that you have an SSH key created and in your member profile. Instructions to do so are here: http://www.topcoder.com/wiki/display/projects/Generate+SSH+Key, and instructions to connect afterwards are here: http://www.topcoder.com/wiki/display/projects/Connect+Using+SSH+Key.

There is a TC Site Resource page that contains documentation / instructions for the VM instance you will be issued upon request. It is located here: http://www.topcoder.com/wiki/display/projects/Cockpit%2CDirect+VM

Technology Overview

• Java 1.5
• JSP
• Struts 2
• Redhat Linux
• JBoss 4.0.2
• Informix 10.0

Final Submission Guidelines

Submission Deliverables

• Source code which are necessary to meet all the requirements stated above, including java class, jsp files, sql files etc.
• The competitor should provide a deployment document. This document should include a step-by-step guide on the deployment.
• The test data (as sql script) needed to test the fixes.

Final Submission

For each member, the final submission should be uploaded to the Online Review Tool.