Skip to content

Mobile view does not show that an issue is moved

Summary

On mobile / responsive views, there is no indicator the issue has been moved.

This is especially relevant for https://gitlab.com/gitlab-org/gitlab-foss/-/issues where we closed thousands of issues

Mobile view:

Screen_Shot_2020-08-06_at_9.53.12_AM

Contrast to Web view:

Screen_Shot_2020-08-06_at_9.52.49_AM

Steps to reproduce

  1. Navigate to gitlab-foss#78891 (moved) on a mobile.
  2. Try to find where the issue has been moved to.
  3. On the web view, clicking Closed (moved) goes to #233546 (closed). We cannot do this on mobile view

Solution

Include the (moved) link and text in the mobile version, within the button alongside the Closed icon

Moved_text

Example Project

https://gitlab.com/gitlab-org/gitlab-foss/-/issues

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

What is the current bug behavior?

No link to moved issue

What is the expected correct behavior?

Link to moved issue is visible on mobile view

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

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)

Workaround

"Request desktop site"

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by Holly Reynolds