Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 858911

Summary:	[RFE] add RecipeSet ID as description in Recipe page
Product:	[Retired] Beaker	Reporter:	Monson Shao <jshao>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.9	CC:	azelinka, ccui, mastyk, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	UX
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-02 11:42:20 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:
Bug Depends On:	1263918
Bug Blocks:

Comment 3 Dan Callaghan 2016-04-05 11:06:54 UTC

We actually didn't account for this in the new recipe page design (it still doesn't show the recipe set ID anywhere). We should probably try and come up with somewhere good to put it.

Comment 4 Ales Zelinka 2016-11-25 18:07:13 UTC

This is in my opinion a regression from the old UI - I need RS ID for acking/nacking a result. But the only page I found it on is job page, which can and does usually contain more than one recipeset - it's easy to nak wrong RS by mistake.

Comment 5 Roman Joost 2016-11-27 23:39:33 UTC

Dear Ales,

how do you typically waive results? Use the job page or the bkr client? In other words, do you typically copy & paste the ID or navigation or?

Comment 6 Ales Zelinka 2016-11-30 11:01:27 UTC

From the command line. Because I waive jobs produced by automation so I run it from the server the service sits on (WebUI would be more user friendly but I don't want to install browser there)

Comment 7 Martin Styk 2020-06-02 11:42:20 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>