Summary

Define and annotate the entity relationships among domain objects (User, Project, Issue, PullRequest, GitRepo, etc.) to reflect real-world associations cleanly and correctly.

This step ensures the domain model is semantically connected, navigable via JPA, and aligned with production-ready behavior such as lazy-loading, cascade rules, and cyclic reference handling.

Acceptance Criteria

•  Add @OneToMany, @ManyToOne, @ManyToMany mappings with mappedBy and fetch where applicable
•  Introduce inverse navigation fields as needed (e.g., User.reportedIssues, User.assignedIssues)
•  Ensure bidirectional consistency for:
  • User ↔ Role
  • User ↔ Project
  • Project ↔ Issue, GitRepo, PullRequest
  • Issue ↔ IssueComment
  • PullRequest ↔ reviewers, relatedIssue, gitRepo
•  Add appropriate cascade settings (e.g., cascade delete for issue comments)
•  Annotate @JsonIgnore on bidirectional relationships to avoid cyclic serialization
•  Ensure all entity classes compile and can be saved/loaded in tests

Notes

• Use FetchType.LAZY for most @OneToMany and @ManyToMany fields to avoid N+1 query problems
• Consider whether PullRequest should belong to Project or GitRepo — decide and apply consistently
• Relationships should remain semantically minimal — avoid "everything links to everything" bloat

Work Estimate

Total Estimate: ~3–3.25 hours