Bug 1875809

Summary: Topology - Improve Pipeline Run & Build Duration Text
Product: OpenShift Container Platform Reporter: Abhinandan Das <abhindas>
Component: Dev ConsoleAssignee: Abhinandan Das <abhindas>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:37:52 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 Abhinandan Das 2020-09-04 12:35:37 UTC
Description
When viewing the sidebar in Topology, the Builds and Pipeline Runs show their "id" on the running object and in brackets how long ago it started.

The duration (how long ago) should be a inline-block content and show up on it's own line if it's unable to show on one line.

version:
4.6

Steps to Reproduce
1. Add a Pipeline to a Deployment
2. Fire up a few Pipeline Runs over some duration

Actual result:
 The time is displayed as an inline and breaks desired UX

Expectecd result
The time should be displayed as inline block.

Comment 2 Abhinandan Das 2020-09-23 10:36:47 UTC
Verified on

OpenShift Version
4.6.0-0.nightly-2020-09-22-213802
Kubernetes Version
v1.19.0+8a39924
Channel
stable-4.6
Cluster ID
f121c7e0-cc7c-4d86-9b19-b10233391c34
API Server
https://api.jakumar-22091122.devcluster.openshift.com:6443

Comment 5 errata-xmlrpc 2020-10-27 16:37:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196