Bug 2218390 - Add a counter of outstanding needinfo requests to the UI
Summary: Add a counter of outstanding needinfo requests to the UI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On: 2218389
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-28 23:53 UTC by Jeff Fearn 🐞
Modified: 2023-08-03 00:13 UTC (History)
0 users

Fixed In Version: 5.0.4.RH89
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-03 00:13:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeff Fearn 🐞 2023-06-28 23:53:34 UTC
Description of problem:

Currently it is quite hard to get access to outstanding requests in the UI.

The only way to do this in the UI is to select the My links -> My Requests menu entry. This takes you to a page that lists the requests you have received along with the requests you have made.

There should be a counter next to your name in the top right of the page containing the number of requests made of you that are in the '?' flag state.

This should link to the requests page with the requestee set and the flag state limited to '?'.

Comment 1 Jeff Fearn 🐞 2023-07-28 06:08:33 UTC
ON QA server.

1. Login as a user with outstanding need info requests.

There is a count of outstanding needinfo requests in the top right user zone.

The count has a pop-up text explaining what the count the mans and instruction the user to click to get a list of the requests.

Clicking the link takes the user to the Request Queue with the parameters set to restrict the list to outstanding needinfo requests for the user.

Comment 2 Jeff Fearn 🐞 2023-07-29 01:54:26 UTC
This fix has been deployed to stage Bugzilla for a short public testing phase.

https://bugzilla.stage.redhat.com

Comment 3 Jeff Fearn 🐞 2023-08-03 00:13:45 UTC
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.


Note You need to log in before you can comment on or make changes to this bug.