Bug 1324384

Summary:	It lost the default version setting after migrate to BZ5
Product:	[Community] Bugzilla	Reporter:	Rony Gong 🔥 <qgong>
Component:	Administration	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED NOTABUG	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	huiwang, jmcdonal, mtahir, qgong
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-13 02:08:38 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:

Description Rony Gong 🔥 2016-04-06 08:42:34 UTC

Description of problem:
It lost the default version after migrate to BZ5

In BZ4.4, we could file bugzilla bug without setting the version, since the default version already set, but after migrate to BZ5, it ask me to select  version when file bug, since the default version lost.


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

How reproducible:
100%

Steps to Reproduce:
1.Try to create a bugzilla bug, just input summary and select component, click Save button.
2.
3.

Actual results:
It ask me to select version

Expected results:
Same as BZ4.4, using the default version when no input

Additional info:

Comment 1 Jeff Fearn 🐞 2016-04-10 22:31:52 UTC

There isn't a default version, there is a cookie "VERSION-Bugzilla" which stores the last version you set on any bug. If this cookie isn't being updated or isn't being used, then we have a bug. If the cookie contains a version that is invalid for the current product then it won't be used.

Comment 2 Rony Gong 🔥 2016-04-13 01:41:14 UTC

(In reply to Jeff Fearn from comment #1)
> There isn't a default version, there is a cookie "VERSION-Bugzilla" which
> stores the last version you set on any bug. If this cookie isn't being
> updated or isn't being used, then we have a bug. If the cookie contains a
> version that is invalid for the current product then it won't be used.

The default version do works as you said. We can close this bug.