gitbucket/gitbucket

Relation for issues

Open

#1,619 opened on Jun 14, 2017

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

Repository metrics

Stars
 (9,371 stars)
PR merge metrics
 (Avg merge 1h 54m) (18 merged PRs in 30d)

Description

Issue

Impacted version: not relevant

Deployment mode: not relevant

Problem description:

Contributor guide

Research direction
Study GitBucket's issue model and database schema. Find where issues are created and updated. Add a new table or field for issue relations (e.g., 'issue relations' with columns: source issue id, target issue id, relation type). Implement UI dropdowns for selecting relation types and display linked issues on the issue page. Update the issue API to handle relations. Refer to existing tests for adding new features.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitScala
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40