Bug 748728 - ASSIGNED should require non-blank "Assign To" field.
Summary: ASSIGNED should require non-blank "Assign To" field.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 07:54 UTC by Bohuslav "Slavek" Kabrda
Modified: 2013-06-24 01:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-25 22:39:51 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.