Project

General

Profile

Actions

Feature #32944

closed

Always preserve the tree structure in the project jump box

Added by Robert Schneider about 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Projects
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

#31355 is really a nice thing. But one thing is a bit distracting: When a project gets to the list of recently used projects, it gets removed from the list of other projects. Understandable, but from an UX perspective IMO it is not so nice if the project has disappeared where one would expect it. Then you have to take a look: might it be in the recently used project list? Or did I bookmark it?

Not such a big issue. However, if you have a project structure with nested projects and you have a parent project in the recently used project list, than the other projects are rendered a bit differently. I find that confusing.

I have about 100 projects with such a structure. I'd be happy if the list of other projects look always the same. In order to find projects faster on scrolling.

If you consider this, then 'Other Projects' should probably need to be renamed to 'All projects'.


Files

0001-project-jump-box-usability-enhancements.patch (6.16 KB) 0001-project-jump-box-usability-enhancements.patch Jens Krämer, 2020-07-01 11:21
32944-before.png (35.4 KB) 32944-before.png Go MAEDA, 2020-07-02 04:24
32944-after.png (46.5 KB) 32944-after.png Go MAEDA, 2020-07-02 04:24

Related issues

Related to Redmine - Feature #31355: Bookmarks and recently used projects for the project jump boxClosedGo MAEDA

Actions
Related to Redmine - Defect #34357: Fix Capybara::Ambiguous: Ambiguous match, found 2 elements matching visible link or button "eCookbook" ClosedGo MAEDA

Actions
Has duplicate Redmine - Defect #33766: #31355 breaks project treeClosed

Actions
Actions #1

Updated by Jens Krämer almost 4 years ago

Actually a few of our customers at Planio had the exact same complaints, attached is a patch against current master which implements the following changes:

  • always renders the full project tree in the third section of the jump box (that is, it does not exclude favorites and recently used projects)
  • in case the user enters a query, only one "Results" section is rendered instead of filtering all three sections
Actions #2

Updated by Go MAEDA almost 4 years ago

+1
I am sometimes confused by the behavior, too. Thank you for posting the patch.

Here are screenshots of the patch.

Before:

After:

Actions #3

Updated by Bernhard Rohloff almost 4 years ago

1+ I stumbled upon the same issue several times.

Actions #4

Updated by Fernando Hartmann almost 4 years ago

+1 Some of my users, complaint on this behavior too.

Actions #5

Updated by Go MAEDA almost 4 years ago

  • Target version changed from Candidate for next major release to 4.2.0

Setting the target version to 4.2.0.

Actions #6

Updated by Go MAEDA almost 4 years ago

  • Related to Feature #31355: Bookmarks and recently used projects for the project jump box added
Actions #7

Updated by Go MAEDA almost 4 years ago

  • Tracker changed from Defect to Feature
  • Subject changed from Jump box issue caused by Recently used projects and Other projects to Always preserve the tree structure in the project jump box
  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patch. Thank you for further improving the UI.

Actions #8

Updated by Bernhard Rohloff over 3 years ago

Actions #9

Updated by Go MAEDA over 3 years ago

  • Related to Defect #34357: Fix Capybara::Ambiguous: Ambiguous match, found 2 elements matching visible link or button "eCookbook" added
Actions #10

Updated by Heiko Robert about 3 years ago

Just came across the same issue after upgrading to 4.1

In our use case the patch in this ticket does not solve the issue. We have a quite complex hierarchical project structure.
before introducing #31355 the user had always in the project jump box the current project in the hierarchy preselected and could just select a sub project using the up and down keys. Now the user has to scroll down thru the whole tree to find the real node to see the childs the user wants to switch to.

#31355 is not ideal/wanted for every installation. Introducing two leaves for the same node makes things different but still confusing/not as expected so I would suggest to make that feature (#31355) configurable to optionally turn it off again.

should I create another ticket since this one is already closed?

Actions

Also available in: Atom PDF