Bug 913098

Summary: Two issues when public user change the status of the bug in some conditions.
Product: [Community] Bugzilla Reporter: Chen Chen <chechen>
Component: User InterfaceAssignee: Matt Tyson 🤬 <mtyson>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: jingwang, jzhao, mtyson
Target Milestone: 4.4-3   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4-3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-20 11:07:19 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: 822804, 858932    
Attachments:
Description Flags
issue 1 none

Description Chen Chen 2013-02-20 11:33:09 UTC
Created attachment 699973 [details]
issue 1

Description of problem:
1. Public user can not change the status of the bug created by himself/herself if the bug's product contain 'Red Hat Enterprise Linux'.
2. When public user change the status of a bug which is not the create by himself/herself but he/she is the assignee of it, no CLOSED choice in drop list of status.

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

How reproducible:
always

Steps to Reproduce:
1. Login bugzilla with a public account.
2. Create a bug, product of the bug contains 'Red Hat Enterprise Linux'
3. Check the status of the bug in the drop list at the bottom of the bug's details page.
4. Change bug status, then click 'Save Changes' button.
5. Login bugzilla with a redhat account.
6. Create a bug, product of the bug contains 'Red Hat Enterprise Linux', and set public user A as assignee.
7. Login bugzilla with public account A.
8. Change bug status to CLOSED.
  
Actual results:
1. After step 3 the Status at the bottom of the page is: 
NEW[NOTABUG]
(see screenshot in attachment~~)
2. After step 4 the change can not be saved.
3. After step 8 no CLOSED choice in drop list of status.

Expected results:
1. After step 3 the status is NEW.
2. After step 4 the change can be saved.
3. After step 8 the status of the bug is CLOSED.

Comment 2 Matt Tyson 🤬 2013-03-01 03:54:49 UTC
1 & 2: This is by design. NOTABUG.

The issue in the screenshot is a bug and will be fixed.

Comment 4 wangjing 2013-05-08 11:53:03 UTC
Verified on qe test env version 4.4.rc2-3(20130426) --> PASS

Verify steps:
1. Login bugzilla with a public account.
2. Create a bug, product of the bug contains 'Red Hat Enterprise Linux'
3. Check the status of the bug in the drop list at the bottom of the bug's details page.
then expected result: the Status at the bottom of the page is 'NEW', not 'NEW[NOTABUG]'. 

Actual results:
same as the expected results above.