gitbucket/gitbucket

Relation for issues

Open

#1,619 opened on Jun 14, 2017

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Scala (9,371 stars) (1,262 forks)batch import
featurehelp wanted

Description

Issue

Impacted version: not relevant

Deployment mode: not relevant

Problem description:

Contributor guide

Tech stack
scala
Domain
full stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
ScalaDatabase schema understandingGitBucket codebase structureIssue model
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the current issue model and database schema in the GitBucket codebase. Look at the models/Issue.scala file and the database migration files to understand how issues are stored. Then, design the relation types and propose changes to the schema, API, and UI. Consider existing issue relations in other platforms like GitHub.