Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2100666

Summary:	BuildConfig form is not used when creating a BuildConfig
Product:	OpenShift Container Platform	Reporter:	Christoph Jerolimov <cjerolim>
Component:	Dev Console	Assignee:	Debsmita Santra <dsantra>
Status:	CLOSED COMPLETED	QA Contact:	spathak <spathak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.10	CC:	dsantra, nmukherj, sidsharm, talessio
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.12.z
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:	2023-05-31 18:54:42 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 Christoph Jerolimov 2022-06-23 22:52:11 UTC

Description of problem:
ConfigMaps, Secrets, Deployments, DeploymentConfigs uses the edit form also for creation with 4.11. But BuildConfigs uses the edit form only for edit, not to create one.

Version-Release number of selected component (if applicable):
4.10 and above

How reproducible:
Always

Steps to Reproduce:
1. Switch to dev perspective
2. Navigate to build
3. Click on create

Actual results:
Opens a YAML editor to create a BuildConfig

Expected results:
Should open a form, with a YAML switcher to create a BuildConfig

Additional info:

Comment 3 Shiftzilla 2023-03-09 01:22:14 UTC

OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9336

Comment 4 Debsmita Santra 2023-05-11 08:29:09 UTC

Verified on build version: 4.12.0-0.nightly-2023-05-10-185003, can see form view with a YAML switcher to create a BuildConfig
Browser version: Chrome 112

Comment 5 Christoph Jerolimov 2023-05-17 11:24:12 UTC

Jira wasn't updated so verified it as well m)

4.12.0-0.nightly-2023-05-17-011545

Comment 6 Siddharth Sharma 2023-05-31 18:54:42 UTC

Jira bug equivalent has been shipped as part of https://access.redhat.com/errata/RHBA-2023:2699, closing this.