Topcoder Connect - Bug Bash

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  IMPORTANT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Once claimed issues have to be completed and PR provided during 12 HOURS in this Bug Bash
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Challenge Objectives

Address the list of issues we have in Topcoder Connect App.

Project Background

Topcoder Connect is client facing application of Topcoder. Customers use Topcoder connect to input requirements of their projects, then managers and copilots take it from there.

Technology Stack

• ReactJs

• Redux

• CSS Modules

Individual requirements

IMPORTANT! If you already participated in our Connect App Bug Bash previously, please, also read the rules carefully as there is a change in the Bug Bash process this time.

1. Before picking up an issue you have to check that:
   + Issue has a label “OPEN FOR PICK UP”.
   + Important! Also, check comments on the issue that nobody asked to be assigned to this issue yet.
   + If previous participant didn’t complete an issue during 12 hours, it’s not allowed to claim the issue until the participant asks to unassign him in comments, or issue is marked as open for pick up by the copilot. If previous participant asked to unassign him, it’s allowed to claim the issue even if it’s not marked as open for pick up.

2. Ask in comments to assign the issue to you.
   + You can start working on the issue without waiting to be assigned, your comment with an intention to work on the issue is enough. But make sure by reloading the page, that nobody asked to assign the issue before you.
   + After you’ve asked for the assignment time starts and the issue has to be completed and PR provided during 12 hours.
   + If you need more time to complete the issue, post a comment about the reason for it, otherwise, the ticket could be marked as open for pickup.

3. If you don’t want to finish the issue, please ask in comments to unassign you from the issue.
   + Note, if the participant asked to unassign him from the issue, another participant can ask to assign the issue to him in comments and directly start working on it without waiting to be assigned. Also, in this case, it doesn't matter if the issue has label OPEN FOR PICK UP or no.

4. You can work only on one issue at a time.

5. Fix the issue and create a pull request to the cf13 branch! If the change requires updates to the react-components repo, create the pull request to feature/connectv2 branch at https://github.com/appirio-tech/react-components. Your pull request must pass lint verification and the Travis build must be successful.

6. When you submit the PR, make another comment at the issue like “It’s done and ready for review” or similar and provide a link to the PR. Follow the issue for the possible comments from the project team. You can now start working on the next ticket (no need to wait for the review to finish).

7. If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked as "ACCEPTED". When the ticket is closed, payment will be recorded, and ticket tagged "PAID".

8. You'll be required to fix any merge conflicts before the change is reviewed and merged.

List of issues

https://github.com/appirio-tech/connect-app/issues?q=is%3Aissue+is%3Aopen+label%3ACF-13.

NOTE

We are going to open more issues as this Bug Bash is running, so you may check for additional issues opened for pick up.

Prizes

Please ignore the prize shown in this challenge, that is just the estimated purse from all the tickets.

For this Bug Bash, we will be paying per accepted fix based on the prize amount noted in each issues' title.

Final Submission Guidelines

• Create a PR against cf13 branch. Note, to create a PR you will need to fork repository.

• Submit a text file with a list of issues you worked on in this challenge.