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

Bug 1088737

Summary:	Project type for a version is null after creation if the project type setting is not touched.
Product:	[Retired] Zanata	Reporter:	David Mason <damason>
Component:	Usability	Assignee:	Alex Eng <aeng>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	development	CC:	aeng, dchen, zanata-bugs
Target Milestone:	---
Target Release:	3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-17 06:39:51 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:
Bug Depends On:
Bug Blocks:	1030166

Description David Mason 2014-04-17 05:31:11 UTC

Description of problem:
When a project type is set on a project, and a version is created, the version creation page shows the project type of the project as selected, but the value is 'unspecified' after the version is created, unless the project type setting is manipulated in some way (e.g. click other option and click back on the original option)


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Alex Eng 2014-04-21 21:37:37 UTC

Pull request:
https://github.com/zanata/zanata-server/pull/420

Comment 2 Ding-Yi Chen 2014-04-23 06:24:58 UTC

*** Bug 1030182 has been marked as a duplicate of this bug. ***

Comment 3 Ding-Yi Chen 2014-04-23 07:12:33 UTC

VERIFIED with Zanata 3.4.0-SNAPSHOT (git-jenkins-zanata-server-github-pull-requests-1304)