After creating this issue, I found an unrelated bug: in the right sidebar issue 2/2365 was shown, but it should've been issue 1/2365.

In fact, pressing on the left arrow took me to the same issue (this one), but with the text now correct.

After creating this issue, I found an unrelated bug: in the right sidebar issue 2/2365 was shown, but it should've been issue 1/2365.

In fact, pressing on the left arrow took me to the same issue (this one), but with the text now correct.

It now shows 2/88. The 2 is correct as the issue appears second in the list, but what about the total? I'm assuming the number shown previously included closed issues and the one currently shown doesn't.

Importing from 'davidebeatrici/test-no-issues' to 'davidebeatrici/davidebeatrici/test-no-issues'...
Cloning code...
Importing milestones...
Http request failed (url: https://gitlab.com/api/v4/projects/davidebeatrici%2Ftest-no-issues/milestones?per_page=50&page=1, status code: 403, error message: {"message":"403 Forbidden"})

I disabled issues for a test project at gitlab and it works fine. Does your access token has enough permission to access GitLab issues?

Looks like it's a bug on GitLab's end: the affected repositories are quite old and thus issues have been disabled for years.
Enabling issues fixed the problem but I also just confirmed it's not reproducible with a fresh repository.

I believe we can close this, since there's nothing to do aside from adding a warning/suggestion perhaps.

It now shows 2/88. The 2 is correct as the issue appears second in the list, but what about the total? I'm assuming the number shown previously included closed issues and the one currently shown doesn't.

The total here represents all issues from the list, which can be filtered with a query.

After creating this issue, I found an unrelated bug: in the right sidebar issue 2/2365 was shown, but it should've been issue 1/2365.

In fact, pressing on the left arrow took me to the same issue (this one), but with the text now correct.

Issue number and position mainly serves as issue navigation purpose when select an issue from list. It may not be inaccurate when issues are added/removed.

Could also be a caching issue, but it's purely cosmetic anyway.