Dragonet Data Management - frontend and backend bug Bash

Basic requirements for this challenge:

• Bug Bash on Dragonet Data Management - frontend and backend

• All UI & functionalities issues need to be solved. 

• Browser : Latest version of Google Chrome,

• Be careful! your solution MUST not break the existing application.

Technology Stack : React Js latest, .Net Core 3.1

Assets : Please check the forums.

General Requirements:

• In this Bug Bash challenge, we are looking for your help to fix a bunch of bugs in our repo.

• Read about What is Bug Bash: https://help.topcoder.com/hc/en-us/articles/115002087948-What-is-a-Bug-Bash

• The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.

• Keep best practice implementation on current Angular or Java Maven app

• Please, subscribe yourself to get notifications from this frontend and backend repos to participate in this Bug Bash.

Bug Bash Rules:

• Each issue has a dollar value. Dollar values are based upon complexity and priority of issue.

  • You can assign any unassigned issue to yourself with a "tcx_OpenForPickup" (first come first serve).

• You must update the label to “tcx_Assigned”, and remove the “tcx_OpenForPickup” label.

• You can only self assign one issue at a time. The nature of it being assigned will indicate if it is not available to anyone else.

• You will fix the ticket as a pull request to the dev branch

• Once a ticket is fixed, you should label it "tcx_ReadyForReview" where it will then be verified. If something is still broken, the copilot will comment on the ticket.

• After submitting and tagging "tcx_ReadyForReview" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.

• If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "tcx_FixAccepted".

• If the ticket is “tcx_Feedback”, it should be your first priority to fix the issue.

• When the ticket is closed, payment will be recorded, when we issue the payment the tag will be updated to “tcx_Paid”

• If an assigned task is not done in 12 hours, you will be unassigned from the ticket, and it will be opened back up to the community.

• You can ask questions directly on the ticket comments.

• Bug Bashes are different from Bug Hunts please make sure to check the contest type in the contest name when registering.

IMPORTANT:

• DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need to track your changes so focus only code fixes.

• DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.

• RE-TEST AND COMPARE ON all required browsers before you submit

Final Submission Guidelines

SUBMISSION FLOW

• First, make sure your "master" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.

• CREATE NEW BRANCH based on our latest "master" branch with the title format "issues/handle/XX" where XX is the number on the GitLab Issue.

• DO NOT FORK into your own repo. you MUST create from our "master" branch. We will reject your submission if you submit from your own repo.

• Start working your fixes in that branch, commit and push to your working repo.

• Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.  

• Next you will send MERGE REQUEST to "master".

• Put the Ticket url you were working on in the Merge Request description.

• If something is still broken, the Reviewer will comment on the ticket. We will update the label as " tcx_Feedback" and you can complete the fixes based on the feedback.