Geo links on project issues's author link to the main server
Summary
Clicking a project issue's author link on a Geo node causes an incorrect redirect to the primary server.
Steps to reproduce
- Deploy a primary server with a geo node using a geo-aware DNS URL.
- Browse the geo node to a project with issues.
- Click on an issue's author and notice that the URL is redirected to the primary node.
- Observe that clicking on pipelines, merge requests etc. do not redirect, they stay on the geo node.
Example Project
What is the current bug behavior?
Issue author links on Geo nodes have an incorrect redirect target: the primary node.
What is the expected correct behavior?
Project issue author links should maintain Geo node context for accurate navigation.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: \\\\\\\`sudo gitlab-rake gitlab:env:info\\\\\\\`) (For installations from source run and paste the output of: \\\\\\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\\\\\`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:check SANITIZE=true\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\\\`) (we will only investigate if the tests are passing)
Possible fixes
Edited by Phawin Khongkhasawan

