Bug 1549925

Summary:	Queued/Running/Completed buttons need better placement / change in functionality
Product:	[Retired] Beaker	Reporter:	Anwesha Chatterjee <achatter>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	develop	CC:	huiwang, jkortus, mastyk, qwan, tools-bugs
Target Milestone:	future_maint
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	999933	Environment:
Last Closed:	2020-06-02 11:54:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anwesha Chatterjee 2018-02-28 04:44:21 UTC

Currently, the search bar in the jobs page (and I assume other pages with search bars in beaker) has a group of 3 buttons "Queued/Running/Completed" next to the button "Lookup ID". 

This suggests that you need to enter an ID to then filter it as either queued/running/completed.

This is not the case and the button simply returns all jobs that are queued/running/completed.

To make this more obvious, either better placement or change of functionality could help.

Comments welcome on either.


Steps to Reproduce:
1. Go to jobs list page (/jobs)
2. Fill in the search field
3. click Queued 

Actual results:
returns job with entered ID even if it is not queued

Expected results:
Only returns job with entered ID if it is also queued

Comment 1 Martin Styk 2020-06-02 11:54:07 UTC

Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>