Avoid jumping from a collection to pinned

Summary

If users have an item that is pinned, then selecting that item under it's original collection will collapse the collection and switch to pinned.

If I pin an item, issues boards for example, and then later click on that item in the section in this example plan. I find it unnecessary to collapse the section (plan) when highlighting issue boards in the pinned section. I would prefer if the plan section stayed open since my intent was to work within that section.

#403059 (comment 1344289229)

A point that I find very annoying for a few weeks now:

• I have pinned pipelines.
• I click on Build -> Pipelines
• The build category closes again instead of
  • a) remembering that it was open
  • b) staying open, because I am inside the build category.
• Same with the code. I have "Repository" pinned, click on it and decide to compare two branches. Now I have to open "Code" again and click twice.

So my two wishes are:

• Remember which categories you have open. I have a large screen so I would like to have several categories open all the time. Maybe call it a "pin" for categories that are always open.
• If you go into a pinned item, the original category should still open. When I click on "Pipelines" I am in the "Build" context and from there it shouldn't be two clicks away to go to Jobs.

#409005 (comment 1533126697)

Steps to reproduce

Pin any item (Activity)	Pick that item from its collection	Observe the collapsed section

What is the current bug behavior?

The user loses focus on the collection they were navigating within.

What is the expected correct behavior?

Pin any item (Activity)	Pick that item from its collection	No auto collapsing

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