C4GT - Community Revamp - Tech Scoping

Flow:

Requirement
(On Githubt ticket)

View
(on C4GT website)

Assignment
(On Github Ticket)

Points
(On github ticket)

Maintain a metrix of complexity and role to award points on ticket closure.
On closure of ticket, read description and give points basis roles and difficulty to github ids marked above.
(On BE)
Maintain a transaction table with each type of closure, complexity, issue id, etc..

Rewards

Database requirements:

Issues - id, link, org, labels(String[]), complexity, skills, technology, status, etc..
Issue_Contributors - id (pk), user_id (fk), issue_id (fk), role
point_transactions - id (pk), user_id (fk), issue_id (fk), point, type (credit / debit / lapse)
User - id (pk), name, discord, github, points, level
User_certificates - id, user_id, certificate_link
user_badges - id, user_id (fk), badge_id (fk)
user_activity - id, user_id (fk), issue_id (fk), activity
Badges - id, image, text, description
points_mapping - id, role, complexity, points

Created_at, updated_at in all tables.