Fix error message when attempting to add a sub-epic to an epic from a different domain.
Summary
When attempting to add a sub-epic to an epic from a different domain, user receives the message, " "could not be found" which is not specific enough to help them understand why the action failed and or how to resolve.
Steps to reproduce
- Attempt to add a sub-epic to an epic from a different domain.
- Note the error message.
What is the current bug behavior?
When attempting to add a sub-epic to an epic from a different domain, user receives thge message, " "could not be found" which is not specific enough to help them understand why the action failed and or how to resolve.
What is the expected correct behavior?
Change the message to more accurately reflect the reason the action cannot be completed and help the user resolve the issue. For example "Epic could not be added. Check the epic is on and you have the correct URL. Learn More" Direct Learn more to troubleshooting help article.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
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
(If you can, link to the line of code that might be responsible for the problem)
@annabeldunstone @uhlexsis @tauriedavis for awareness...