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

Bug 584555

Summary:	[RFE] Intuitive (guided) web UI for job creation
Product:	[Retired] Beaker	Reporter:	Zack Cerza <zcerza>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	0.5	CC:	azelinka, benl, bpeck, mastyk, mcsontos, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	UX
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-02 12:00:52 UTC	Type:	---
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:
Bug Blocks:	1063555

Description Zack Cerza 2010-04-21 20:41:46 UTC

Currently, the only way to schedule a job is via a previously-prepared XML file. RHTS allowed us to easily submit one-off jobs without that overhead. I'm assuming it's planned to re-add that feature, but I need a bug to add the the sign-off page.

Comment 1 Bill Peck 2010-04-22 14:24:03 UTC

This is not something that is going to happen for live.  You can input an xml from scratch on the UI if need be.

Comment 2 Chris Ward 2010-05-26 11:26:11 UTC

"This is not something that is going to happen for live." I'm not sure i understand this response. Does it mean 'this will never happen' or 'this feature will not block beaker and legacy rhts tear down'

Comment 5 Dan Callaghan 2010-10-19 06:28:46 UTC

(In reply to comment #4)
> Its possible we
> could even use the xsd to generate the forms?  

That is a very interesting idea.

I'm picturing kind of like a guided XML editor (in js on the client side) with collapsible elements. The users starts with an empty <job/> element and can fill in new recipes by starting with the minimum mandatory set of elements for a recipe. The ui would make it easy to add optional child elements, and to fill in element content and attribute values. It could display documentation for each element/attribute in a little box beside where the user is editing. And all of it would be generated from the XSD (or the RELAX NG schema).

Let me think some more about how impossible that will be :-)

Comment 6 David Kovalsky 2010-11-18 16:26:03 UTC

This requires UI changes, further work is scheduled for 0.6. 

We won't block RHTS decomission for this bug anyway, so I'm moving it to HotBeakerBugs for further tracking.

Comment 8 Tomas Klohna 🔧 2019-04-03 09:01:39 UTC

Reworded the summary. Also lowered the priority, this feature would be nice to have, but it isn't heavily requested.

Comment 9 Martin Styk 2020-06-02 12:00:52 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>