Saved searches should be available from a menu

NEW
Assigned to

Status

()

Bugzilla
User Interface
P1
enhancement
12 years ago
3 years ago

People

(Reporter: Frédéric Buclin, Assigned: Alex Eiser)

Tracking

Details

(URL)

(Reporter)

Description

12 years ago
We should find a way to display saved searches in a menu at the top of each page or like bookmarks. I have around 30 saved searches, and even if the checkin of bug 206425 will help a lot, it's still not enough.

What I would like is something like:

Saved Searches
      |
      |- Bugzilla
      |     |
      |     |- open blockers
      |     |- wanted for 2.20 or 2.22
      |     |- open bugs targetted < 2.22
      |     |- patches awaiting checkin
      |     |- patches awaiting my review
      |     |- open bugs assigned to me
      |
      |- Firefox
      |     |
      |     |- blockers for 1.5.0.1
      |     |- Fx bugs I want to see fixed
      |
      |- Thunderbird
            |
            |- annoying bugs


And please don't tell me I can do that manually!
(Reporter)

Comment 1

12 years ago
gandalf, is that something we could/should do using AJAX?
yes, It's a nice idea, I'll consider this in the new UI.
Taking. Myk, if you have a plan to work on this in nearest 2 months, mail me please.
Assignee: myk → gandalf
(Reporter)

Comment 3

12 years ago
The UI at userprefs.cgi?tab=saved-searches will also need to be updated in order to be able to move saved searches in the correct folder/subfolder. No idea what the best approach is. Maybe should we limit ourselves to one level only, i.e. adding folders but no subfolders, as in comment 0. This way the UI should be pretty easy to fix.

This would leave us with the menu itself.
Status: NEW → ASSIGNED
Target Milestone: --- → Bugzilla 2.24
(Reporter)

Updated

12 years ago
Blocks: 325501
(Reporter)

Comment 4

11 years ago
This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2

Comment 5

10 years ago
Re assigning it to me since i have a patch for it
Assignee: gandalf → guy.pyrzak
Status: ASSIGNED → NEW

Comment 6

9 years ago
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.
Target Milestone: Bugzilla 3.2 → Bugzilla 4.0
(Reporter)

Updated

9 years ago
Duplicate of this bug: 456042
(Reporter)

Updated

9 years ago
Duplicate of this bug: 463572

Updated

9 years ago
Assignee: guy.pyrzak → aeiser

Comment 9

7 years ago
You can try Deskzilla (http://almworks.com/deskzilla/) -- it's a desktop client for Bugzilla, which lets you see the tree of saved searches at any moment (yes you can also create new sub-searches that operate with the result of the parent search). It's free for some renown projects (such as Mozilla) and for small Bugzilla installations.

Comment 10

6 years ago
I noticed that this bug is currently blocking bug#325501 (ajax) but shouldn't instead be dependent upon that bug?
(Reporter)

Updated

5 years ago
Priority: -- → P1
(Reporter)

Updated

5 years ago
Duplicate of this bug: 345229
(Reporter)

Updated

5 years ago
Blocks: 662605
No longer blocks: 325501
(Reporter)

Updated

5 years ago
No longer blocks: 662605
Depends on: 662605
(Reporter)

Comment 12

5 years ago
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0

Updated

3 years ago
Target Milestone: Bugzilla 5.0 → ---
You need to log in before you can comment on or make changes to this bug.