lumodon / issue-distributor Goto Github PK

Currently we're using heroku pg:psql and typing out our migrations. We should streamline migrations somehow so that CI can be added easily down the road. (Also seeding would be a nightmare)

Create ability to add single csr - modifiy code to use that.

Assign issue to CSR and store that csrs's id on the issue in the database. Keep that issue with that CSR. Then when adding new issues don't distribute evenly, instead, distribute in such a way that each allocation brings everyone's total closer to median.

M: ***** (5)
S: ******** (8)
D: *** (3)
J: **** (4)

Distribute 1 to D, next 1 to J and 1 more to D, then 1 to each M, D, and J randomly, so on until they're all at 8.

Get CSRS's issues assigned.
While issues remaining to distribute:
Find minimum.
Push CSRs to list.
assign issue to random in list.

Let's switch to React for the rapid jsx. Need single page app and sockets but building out DOM objects manually for SO many things gets tedious real quick. Time to implement React.

pull issues out of normal flow when marked as difficult.
ability to mark issue as something YOU don't want to touch ever again. (but not necessarily a bad issue)

Eventually upgrade to use sockets to get immediate feedback if anyone pulled out.

You can go directly to an issue with the following link IF you're logged in AND you don't have a backoffice tab open. Not the most common situation but still better than nothing.

We should update the issue numbers in our issue distributor to contain this link:
https://icobo.cashbet.com/crm/#/crm/players/view/1025291?claimedIssueId=20617&tabId=player-1025291-20617&tabText=_zinnguyen2712vn_gmail_com

This means we additionally need to capture the actorid and email from the issue fetch step, and create another migration to modify table to allow issues to have email and actorid as extra rows.