(Optional) In Data Migrator History, async-before/after jobs are migrated

[venetrius]

User Story (Required on creation)

• As a process engineer, I want to be migrate C7 async-before/after jobs history to C8 so that I can maintain a complete audit trail for compliance purposes.

Functional Requirements (Required before implementation)

Technical Requirements (Required before implementation)

• Plan: Migrate the async-before/async-after job logs per BPMN element
• Create new mapping (HistoricJobLog (C7) -> JobDbModel (C8)) and add minimal test coverage
  • Create JobMigrator, JobTransformer
• FK constrain, populate jobKey in Incident - skip incident if the job is not migrated
• Populate jobKey, type, worker, state, kind, listenerEventType, retries, hasFailedWithRetriesLeft, errorMessage, deadline, endTime, processDefinitionId, processDefinitionKey, processInstanceKey, elementId, elementInstanceKey, tenantId, partitionId
• Document limitations

Limitations of Scope

Hints

• This come up during PR review, comment: feat(history): introduce skipping mechanism in history migrator #150 (comment)
• Copilot POC: feat(history): migrate C7 async-before/after job logs to C8 #1018

Links

Breakdown

Pull Requests

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[tasso94]

C7 Jobs don't map 1:1 to C8 Jobs. Let's explore this further and decide what C7 job types might be useful to migrate.