Bug 690155

Summary:	[RFE] recipe/job IDs in error messages should be links
Product:	[Retired] Beaker	Reporter:	Ales Zelinka <azelinka>
Component:	inventory	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.5	CC:	bpeck, cbouchar, mcsontos, stl, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	UX
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-19 22:13:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ales Zelinka 2011-03-23 13:24:34 UTC

Description of problem:
I got this error when returning a machine:

Failed to return ibm-ls22-01.rhts.eng.brq.redhat.com: u'System has active recipe 124476'

It was surprisingly hard and unintuitive to get to the recipe details. Can you please turn the ID into a link?

Thanks

Comment 1 Min Shin 2012-11-07 07:23:28 UTC

This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.

Comment 2 Ales Zelinka 2012-11-07 17:54:15 UTC

Reopening. I believe I've described the problem in comment#0 .Let me know what additional information do you require and I will provide it.

Comment 3 Dan Callaghan 2012-11-07 22:08:40 UTC

This would be messy to do in the general case (putting hyperlinks into exception strings) but maybe there is some way we can address this case in particular.

Ales, how are you attempting to return the system? From the system page? Did you see that there is a link right there to the "Current Job" which the system is participating in?

Comment 4 Ales Zelinka 2012-11-08 15:15:34 UTC

I don't remember what exactly happened (it's been 1.5 half year). But I suspect it was one of those corner cases where there was a running recipe from a deleted job so I couldn't click through the job to the recipe and had to use the recipeID directly. 

Anyway this bug is a more general usability RFE: I can rephrase it as "each and every job/recipe/recipeset ID that is displayed in webUI should be a link". 

I agree that having HTML in raw exceptions is plain ugly but maybe you can use some consistent identifiers in exceptions like J:XYZ for job and RS:XYZ for recipe sets and then transform them into links when they get passed from application to presentation layer?