Bug 1523393

Summary:	RFE: Reorder the appearance of routes
Product:	OpenShift Container Platform	Reporter:	Mauricio Magnani <mmagnani>
Component:	RFE	Assignee:	Robb Hamilton <rhamilto>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aos-bugs, erich, jokerman, mmccomas, rhamilto, spadgett
Target Milestone:	---
Target Release:	3.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-12 11:56:43 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 Mauricio Magnani 2017-12-07 21:09:09 UTC

Description of problem:

Customer want to reorder the routes displayed in the overview page.  For example, make a specific route be the primary and not the "1 other route" that you have to click on.

1. Why exactly do you need this feature? (List the business requirements here)

Users (devs, QA, operations, etc.) would like to set the primary URL for ease of identification and risk mitigation (see what you're working on)
Ex. appname.app.com instead of fix17.app.com or blue.app.com, green.app.com

2. How would you like to achieve this? (List the functional requirements here)?

* Tag a route as primary
* Priority selector
* Drop-down selector

3. Do you have any specific timeline dependencies?

No

4. Would you be able to assist in testing this functionality if implemented?

Yes

Comment 1 Jessica Forrester 2017-12-14 19:22:40 UTC

There is an existing github issue discussing this and the UXD team has been working on a design proposal https://github.com/openshift/origin-web-console/issues/1926

Comment 2 Robb Hamilton 2018-03-12 13:01:50 UTC

PR to resolve: https://github.com/openshift/origin-web-console/pull/2887

Note this PR does not include the GUI-based editor included in the design proposal.  The decision was made to limit the editing functionality strictly to use of the existing YAML editor.

Comment 5 Kirsten Newcomer 2019-06-12 11:56:43 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.