Issue Activity wrong when setting Epic parent
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
When adding a parent Epic to an Issue the activity does not correctly link to the epic but the local issue database We are on GitLab 18.2 self-hosted install with a donated opensource license.
See:
This is linking back to the local issue database and not the epic which is number 10.
Steps to reproduce
Add an Epic to an issue.
Example Project
What is the current bug behavior?
Activity update is linking to the local issue database instead of the Parent epic that is being set.
What is the expected correct behavior?
Link to the epic database instead of the issue database.
Relevant logs and/or screenshots
Epic set to:
Activity says:
See also
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\`)
GitLab 18.2 on FreeBSD with an opensourse ultimate license
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
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.