Thanks for reporting. Will check this.

Is there anything I can provide you with that could help with solving the issue? I checked the logs but they seemed rather general.

My test here is that only links to issues of same project will be processed. Links to issues of other projects will be ignored.

Are you importing projects from project list page, or importting issues from issues page of a project?

I do find the bug that OneDev will link to issue with same number in current project for cross-project issue links. This will be fixed in upcoming 9.2 release.

As to 502 error please make sure that the machine is not sleep during importing.

State changed as code fixing the issue is committed (a0858b78)

State changed as build #4194 is successful

My test here is that only links to issues of same project will be processed. Links to issues of other projects will be ignored.

Are cross-project links not supported at all?

Are you importing projects from project list page, or importting issues from issues page of a project?

From main project list (<hostname>/~projects)

I do find the bug that OneDev will link to issue with same number in current project for cross-project issue links. This will be fixed in upcoming 9.2 release.

Awesome, you mean this release/build: https://code.onedev.io/onedev/server/~builds/4194 ?

As to 502 error please make sure that the machine is not sleep during importing.

After the previous report (https://code.onedev.io/onedev/server/~issues/1073) I made sure that the computer didn't sleep, the page was active. In the dev console I saw a request to the server couple of times per second or so that failed hitting almost exactly 40m mark -- is there another hard limit to 40 minutes (in addition to 5 minutes inactivity timeout for when the computer sleeps or the session stops for some reason)?

Are cross-project links not supported at all?

It is not supported at all. However for projects import, it should be possible to handle that if all related projects are imported all at once. I filed an improvement request for this (#1595).

As to 502 error, there is no other limit at OneDev side except for session timeout, which should not happen if browser remains active. Please connect to OneDev 6610 port directly to bypass your reverse proxy to see if the problem still exist.

Awesome, you mean this release/build: https://code.onedev.io/onedev/server/~builds/4194 ?

Exactly

Are cross-project links not supported at all?

It is not supported at all. However for projects import, it should be possible to handle that if all related projects are imported all at once. I filed an improvement request for this (#1595).

Indeed I'm using "import all projects" (hence my assumption that it should be supported, or at least possible). I subscribed to that issue :-)

As to 502 error, there is no other limit at OneDev side except for session timeout, which should not happen if browser remains active. Please connect to OneDev 6610 port directly to bypass your reverse proxy to see if the problem still exist.

Do you mean I should try doing import while connecting directly to 1dev altogether?

Do you mean I should try doing import while connecting directly to 1dev altogether?

Yes, just in case there are some mis-configurations at nginx side.

However for projects import, it should be possible to handle that if all related projects are imported all at once. I filed an improvement request for this (#1595).

I wonder if it would be possible to maintain the links upon (re-)importing single project if all other projects are already in the system - a case somewhat similar to "import all projects at once".

To re-establish links between newly imported issues and existing issues, the import history info needs to be maintained which is very complicated and can also bloat the database.