Bug 748728

Summary:	ASSIGNED should require non-blank "Assign To" field.
Product:	[Community] Bugzilla	Reporter:	Bohuslav "Slavek" Kabrda <bkabrda>
Component:	Creating/Changing Bugs	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6	CC:	sgreen
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:	2011-10-25 22:39:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bohuslav "Slavek" Kabrda 2011-10-25 07:54:16 UTC

Description of problem:
When I change the bug state to ASSIGNED, but forget to take it (and therefore leave the "Assigned To:" field blank, bugzilla should warn me, that this is not possible.


How reproducible:
Always

Steps to Reproduce:
1. Find a not assigned bug
2. Change state to ASSIGNED
3. Leave the "Assigned To:" field blank
  
Actual results:
Bugzilla processes the request.

Expected results:
Bugzilla shouldn't process the request and warn me, that "Assigned To:" field is blank, but I'm trying to change the state to ASSIGNED.

Comment 1 Simon Green 2011-10-25 22:39:51 UTC

Hi,

All bugs, when created, are assigned to a Red Hat Bugzilla account. If an user name is not specified when creating a bug, then the default assignee for the component is used.

Therefore when a bug status is changed from NEW to ASSIGNED, the bug is already assigned to a user.

  -- simon