ImportService

org.jenga.service.ImportService

Handles bulk import of tickets into a Jenga project from two different sources: GitHub Issues and the Jenga native export format.

Both methods are transactional and return an ImportReportDTO that summarises the result.

Methods

importFromGitHub

1

public ImportReportDTO importFromGitHub(String projectId, List<GitHubIssueDTO> githubIssues)

Converts a list of GitHub issue DTOs into Jenga tickets and persists them under the given project.

Parameters

Processing steps (per issue)

1. Creates a new Ticket and sets its title from the issue title.
2. Parses the issue body line by line:
3. Lines starting with - [ ] or - [x] are parsed as Acceptance Criteria (completed state is preserved).
4. All other lines are joined and stored as the ticket description.
5. Resolves the assignee by matching the first GitHub assignee's login to a Jenga username. If not found, a warning is logged and the ticket is still imported without an assignee.
6. Looks up or creates Labels by name within the project, using the GitHub label's color.
7. Maps the GitHub project-board status to a TicketStatus (see Status Mapping).
8. Persists the ticket.

Error handling

• If the project is not found, returns immediately with a fatal error and 0 successful imports.
• Individual ticket failures are caught, logged as warnings, and do not abort the rest of the import.

importFromJenga

1

public ImportReportDTO importFromJenga(String projectId, List<TicketRequestDTO> ticketRequests)

Re-imports tickets from a Jenga native export (e.g. a previously exported JSON), preserving all fields.

Parameters

Processing steps (per ticket)

1. Sets all standard fields: title, description, priority, size, status.
2. Looks up or creates Labels by name (global, not project-scoped).
3. Resolves the reporter by username — throws if not found, skipping the ticket and recording the error.
4. Optionally resolves the assignee by username — also throws if provided but not found.
5. Maps AcceptanceCriteria DTOs to entities.
6. Persists the ticket.

Error handling

• If the project is not found, returns immediately with an error and 0 successful imports.
• Per-ticket failures (e.g. unknown reporter/assignee) are caught, added to the error list, and do not abort the rest of the import.

Note: Unlike importFromGitHub, a missing reporter or assignee is a hard failure for that ticket rather than a soft warning.

Status Mapping

Used internally by importFromGitHub to convert GitHub project-board column names to TicketStatus values.

Return value — ImportReportDTO

Both methods return an ImportReportDTO with: