Problems navigating between Issues and Project Boards

[sudojunior]

This has gotten perpetually confusing the more I attempted to diagnose it, but I've done my best with the video attached.

While it has no audio, the list of 'events' or actions I run on these pages is the same one you see below.

I apologise if this turns out to be a duplicate, this took quite a while to gather evidence for. And if the recording is confusing for you, I will leave a link to the sandbox repository at the end of this post so that you may try it yourself.

System Details

• OS: Windows 10 Home
• Browser: Opera GX

I should note that I have given it a try in Google Chrome along with Microsoft Edge, and the expected outcome was far different for what I had drafted below for Opera. Chrome and Edge have similar outcomes to Opera, only difference being that they are faster at navigating to you may be more likely to miss key details when running through each test case.

Key

• ❌= Failed
• ✅= Passed

Test Cases

Not all may be in the attached video, and there may be some others that weren't listed here or repeated.

❌ Issue 1 -> Project 1 (direct) ✅ Issue 1 -> Project 1 (sidebar) ❌ PR 1 -> Project 1 (direct) ✅ ~ -> Pull Request Overview (nav) ✅ PR 1 -> Project 1 (sidebar) ✅ ~ -> Pull Request Overview (nav) ✅ Discussion 3 -> Project 1 (direct) ✅ Project 1 -> Issues Overview (nav) ✅ ~ -> Issue 1 (list) ✅ ~ -> Project 1 ({back}) ✅ Project 1 -> Pull Request Overview (nav) ✅ Project 1 -> Discussion Overview (nav) ✅ ~ -> Discussion 2 or 3 (list) ✅ ~ -> Project 1 (direct) ✅ ~ -> Project 1 ({back}) ✅ Project 1 -> Discussion 3 (direct) ✅ Project 1 -> Code (nav) ✅ Project 1 -> Wiki (nav) ✅ Wiki -> Project 1 (direct) ✅ Project 1 -> Issue 1 (direct) ✅ Project 1 -> Pull Request 1 (direct) ✅ Code -> Projects -> Project 1 -> Code # Previously broke the layout entirely and caused further layout problems when continuing through Issues, PRs and Discussions. ✅ Code -> Compare{base}...{compare} (branch + compare) ✅ ~ -> Issues (nav) ✅ ~ -> Pull Requests (nav) ❌ ^ both failing on Enterprise 3.2 📋 Create empty repository (blank slate) ✅ ~ -> Code (nav) ❌ ^ failing on Enterprise 3.2 

Video

GitHubProjectFeedback.mov

Repository Sandbox - now 404

---

Edit 1 on 16th July 2021

Direct Issue and Pull Request linking were changed from not possible to passed.

While it may seem strange that I chose not to do the direct issue or PR links, after posting I decided to have a look anyway... and found that it becomes a maze of layout problems with problems stacking upon each other with every preceding action you make (provided you have only gone to Issues, Pull Requests or Discussions).

It becomes very difficult to retrace your steps, in order to repeat said problem.

But I can say that, the direct linking strategy is fine like the Discussion was.

Further testing discovers that if you click the link from an overview page as part of the metadata, it is also fine (and then when attempting to navigate back to the overview via the navigation bar, the layout is reset for Pull Requests but not Issues).

It is also not certain if you get the bugged layout or not. Attempting to run the sequence of Issues -> Issue 1 -> Project 1 -> Issues and repeating this cycle yields different results (it is neither consistent with what layout you are given, nor is the rate at which it is given - identifying parallels with that of the Mandelbrot set theorem but across 3 outcomes at a minimum, sometimes more).

---

Edit 2 on 21st July 2021

Test cases have been updated and simplified as well as adding an additional test case that was previously failing and causing additional failures on other test cases.

---

Edit 3 on 12th Nov 2021

Comparing branches has additional failing cases that exists on Enterprise 3.2, but is noted with as a pass for GitHub itself.