Assignees are currently silently failing to be migrated

[NetSysFire]

• Version: 84a62db due to TSError: ⨯ Unable to compile TypeScript: on latest commit #222
• npm version: 11.2.0 on Arch Linux, running without docker
• Related: Setting assignee who is not part of the organization fails #217 but this not the same issue.

I have migrated a 259 issue repository hosted at gitlab.com.
I have verified that my user map is correct. All the usernames in the migrated issues are correct.
The repo has been successfully migrated overall, but all the assignees got lost on the way and we had to manually fill them in. When migrating issues, the output contained no relevant errors (besides the two semi-unrelated fails described in the linked issue above). E.g:

Migrating issue #104 ('Merge some config files into static classes')...
	Migrating issue comments...
	...Done creating comments (migrated 1 comments, skipped 3 comments)
	...DONE migrating issue #104.

Migrating issue #105 ('Service: AI v2')...
	Migrating issue comments...
	...Done creating comments (migrated 0 comments, skipped 2 comments)
	...DONE migrating issue #105.
[...]

Migrating issue #155 ('Context Menus')...
	Migrating issue comments...
	...Done creating comments (migrated 0 comments, skipped 2 comments)
	...DONE migrating issue #155.

[...]

DONE creating issues.

	Statistics:
	Total nr. of issues: 259
	Nr. of used placeholder issues: 0
	Nr. of used replacement issues: 0
	Nr. of issue migration fails: 0

My settings were (with sensitive information omitted entirely):

import Settings from './src/settings';

export default {
  gitlab: {
    projectId: 32458208,
    listArchivedProjects: true,
    sessionCookie: "",
  },
  github: {
    owner: 'sourceofmana',
    ownerIsOrg: true,
    repo: 'sourceofmana',
    recreateRepo: true,
  usermap: {
    'NetSysFire': 'NetSysFire',
    'WildX': 'WildX-480',
    'Reidy': 'Reidy',
  },
  projectmap: {
    'sourceofmana/sourceofmana': 'sourceofmana/sourceofmana',
  },
  conversion: {
    useLowerCaseLabels: false,
  },
  transfer: {
    description: true,
    milestones: true,
    labels: true,
    issues: true,
    mergeRequests: false,
    releases: true,
  },
  dryRun: false,
  exportUsers: false,
  useIssueImportAPI: true,
  usePlaceholderMilestonesForMissingMilestones: true,
  usePlaceholderIssuesForMissingIssues: true,
  useReplacementIssuesForCreationFails: true,
  useIssuesForAllMergeRequests: false,
  filterByLabel: undefined,
  trimOversizedLabelDescriptions: true,
  skipMergeRequestStates: [],
  skipMatchingComments: [],
  mergeRequests: {
    logFile: './merge-requests.json',
    log: false,
  },
} as Settings;
  },

Despite me enabling recreateRepo, I have opted to answer no to the prompt as I have spontaneously decided to import the remote repository instead of using a bare one.

An example issue would be https://gitlab.com/sourceofmana/sourceofmana/-/issues/155 vs sourceofmana/sourceofmana#154 - note that the assignee is there on the gitlab side. The mismatched ID is due to the two semi-unrelated fails as mentioned above.

Unfortunately, I do not know what other debugging information to provide. The migration is finished and due to our admittedly rather small number of issues we could fill in most of the missing things manually.

[mschoettle]

When you migrated, was your repo private or public?

[NetSysFire]

The repository got recreated as a private repository. But even the people who had access to the repository did not get assigned to their issues.

[mschoettle]

You could try debugging what exactly is happening. Otherwise it is difficult to know why this happens.

The only thing from looking at the code might be the difference in how the issue import vs. issue creation is handled:

node-gitlab-2-github/src/githubHelper.ts

Lines 478 to 479 in 5b8750d

	let assignees = this.convertAssignees(issue);
	props.assignee = assignees.length == 1 ? assignees[0] : undefined;

[NetSysFire]

Unfortunately I can not test again as the repository has been migrated successfully otherwise.

[spruce]

For me it sounds related to this: #217
With no further option to debug and therefor solve the problem I will close this issue for now