Resolving Duplicate Key Issue During Bugzilla to JIRA Migration

Other Questions Jira
1

I’m encountering a challenging data migration problem while transferring bugs from Bugzilla to JIRA. When using the standard JIRA importer, the process halts due to a unique key constraint violation in the OS_CURRENTSTEP table.

Specific Error Details

  • The import fails when attempting to create a new issue
  • Error occurs at the createIssue() method
  • Duplicate entry error for ID 357430

Technical Symptoms

  • SQL exception during insert operation
  • Conflict in existing database entries

Potential Questions to Consider

  • How can I modify the import process to handle pre-existing IDs?
  • Are there strategies to reset or regenerate sequential IDs during migration?

Example Problematic Code Snippet:

public Issue migrateTicket(ResultSet sourceData) {
    WorkflowStep currentStep = createWorkflowStep(sourceData);
    validateStepUniqueness(currentStep);
    return processIssueImport(currentStep);
}

Any insights into resolving this database migration challenge would be greatly appreciated.

2

hey, try usin a custom import script that generates new unique ids. ive done similar migrations b4 and mapping ids manually works gr8. check ur db settings 2 reset auto increment seq if possibl. good luck!