Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Commit 68dcbdb

Browse files
committed
Update wiki rules for #318
1 parent d7b5e6a commit 68dcbdb

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/assets/WorkingWithTickets.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,19 +2,19 @@
22

33
The basic flow for handling a ticket is as follows:
44

5-
1. Assign the ticket to yourself, change the label to "tcx_Assigned", remove the "tcx_OpenForPickup" label. Please only assign tickets to yourself when you are ready to work on it. I don't want tickets assigned to someone and then not have them work on a ticket for 24 hours. The goal here is a quick turnaround for the client. If you can't work on a ticket immediately, leave it for someone else.
5+
1. Assign the ticket to yourself, and the system will change the label to "tcx_Assigned", removing the "tcx_OpenForPickup" label. Please only assign tickets to yourself when you are ready to work on it. I don't want tickets assigned to someone and then not have them work on a ticket for 24 hours. The goal here is a quick turnaround for the client. If you can't work on a ticket immediately, leave it for someone else.
66

7-
1. Complete the ticket and create a merge request within 24 hours. Please ensure your merge request can be merged automatically and that it's against the latest commit in Git when you create it.
7+
1. Complete the ticket and create a merge request within 24 hours. Please ensure your merge request can be merged automatically (resolving any conflicts) and that it's against the latest commit in Git when you create it.
88

99
1. Change the label on the ticket to "tcx_ReadyForReview"
1010

1111
After seeing a ticket marked as "tcx_ReadyForReview", the copilot will review that ticket, usually within 24 hours.
1212

13-
Note that you are expected to keep your changes in-sync with Git - make sure to do a pull before you push changes to make sure there aren't any merge issues.
13+
Note that you are expected to keep your changes in-sync with Git - make sure to do a pull before you push changes to make sure there aren't any merge issues or conflicts.
1414

1515
### Accepted fix
1616

17-
If a fix is accepted, a payment ticket will be created on the Topcoder platform within 5-10 minutes of the issue being closed. You should see the payment in your PACTs within 24 hours.
17+
If a fix is accepted, the copilot will add label "tcx_FixAccepted" and close the ticket. The system will create a payment ticket on the Topcoder platform within 5-10 minutes of the issue being closed. You should see the payment in your PACTs within 24 hours.
1818

1919
### Rejected fix
2020

@@ -28,7 +28,7 @@ Each ticket in GitLab has a dollar value. That is the amount you will be paid w
2828

2929
# Important Rules:
3030

31-
- You can assign any unassigned issue to yourself with an "Open for pick up" label (first come first serve)
31+
- You can assign any unassigned issue to yourself with an "tcx_OpenForPickup" label (first come first serve)
3232

3333
- You can only assign **ONE AT A TIME**. The nature of it being assigned will indicate it is not available to anyone else.
3434

0 commit comments

Comments
 (0)