Bug 1320085 - A disabled user can be added as the default QA contact/Assignee/Doc Contact to component
Summary: A disabled user can be added as the default QA contact/Assignee/Doc Contact t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Administration
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 09:55 UTC by Hui Wang
Modified: 2016-03-23 01:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 01:46:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Hui Wang 2016-03-22 09:55:10 UTC
Description of problem:
If a user was disable, it should not be allowed to set the user as the default QA contact/Assignee/Doc Contact in component edit page.

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

How reproducible:
100%


Steps to Reproduce:
1. Login with admin account
2. Disable a user: User1
3. Go to Administrator-->product->components
4. Set the disabled user as the default QA contact/Assignee/Doc Contact for the component

Actual results:
It is allowed to add disabled user as the defualt QA contact/Assignee/Doc Contact  for the component

Expected results:
It should't be allowed to add disabled user as the defualt QA contact/Assignee/Doc Contact  for the component


Additional info:

Comment 1 Jason McDonald 2016-03-23 00:49:09 UTC
I think this is intended behaviour.  Mailing-list accounts should be disabled (cannot login) but are frequently used as the default assignee and/or default QE contact as a shorthand for 'unassigned'.

(The Bugzilla product itself uses mailing lists as the default Assignee and QE contact, but these are not currently disabled, which I believe is an error.  I've filed a ticket to correct that in https://engineering.redhat.com/rt/Ticket/Display.html?id=396558.)

Comment 2 Hui Wang 2016-03-23 01:46:00 UTC
Thanks Jason's explanation.


Note You need to log in before you can comment on or make changes to this bug.