Bug 1835425

Summary: Fix it so we don't show Remove Trigger when there are no triggers
Product: OpenShift Container Platform Reporter: Vikram Raj <viraj>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:38:33 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:
Attachments:
Description Flags
Fix it so we don't show Remove Trigger when there are no triggers none

Description Vikram Raj 2020-05-13 18:24:21 UTC 
Description of problem:
When there are no triggers, the modal opens with a disabled dropdown.

We should do better, like disabling the kebab menu option... unfortunately the information is not readably available... so we'll have to fetch it which may not be cheap. Some thinking needs to be done here.


How reproducible:


Steps to Reproduce:
1. Create a pipeline.
2. in the kebab menu of the pipeline you will see the Remove Trigger options even if there is no trigger is present for the pipeline.


Actual results:
the Remove Trigger options even if there is no trigger is present for the pipeline.

Expected results:
Remove Trigger option should not be present if there is no trigger present.

Additional info:
Comment 3 spathak@redhat.com 2020-05-28 23:10:39 UTC 
Validated on build version: 4.5.0-0.nightly-2020-05-28-070355
Browser version: firefox73
Comment 4 spathak@redhat.com 2020-05-28 23:11:14 UTC 
Created attachment 1693192 [details]
Fix it so we don't show Remove Trigger when there are no triggers
Comment 5 errata-xmlrpc 2020-07-13 17:38:33 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, 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:2409