Bug 1792693
| Summary: | Remove Create Pipeline button when getting started guide is enabled | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> | ||||
| Component: | Dev Console | Assignee: | Yadan Pei <yapei> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ruchir Garg <rgarg> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.4 | CC: | aballant, aos-bugs, jokerman, jonjacks, nmukherj, spathak, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause:
The pipeline page was inconsistent with other pages. The Create Pipeline button was enabled always and did not take into consideration when no projects were available.
Consequence:
Inconsistent page with Create Pipeline button present.
Fix:
Removed the create Pipeline button when getting started guide is enabled.
Result:
Create Pipeline button is no longer present when getting started guide is enabled.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-13 17:13:17 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
Yadan Pei
2020-01-19 07:30:24 UTC
Jira backlog ticket: https://issues.redhat.com/browse/ODC-2773 What role does the user have? Created attachment 1693975 [details]
Consistent Started Guideline
When starting guideline message is shown, Pipelines -> Pipelines page doesn't show `Create Pipelines` button, this is consistent with other resource pages
Verified on 4.5.0-0.nightly-2020-05-30-025738
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 |