Bug 822804

Summary: Weird status: CLOSED/ERRATA of [...]
Product: [Community] Bugzilla Reporter: Petr Šplíchal <psplicha>
Component: User InterfaceAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 4.2CC: chechen, ebaak, jingwang, mtyson, ohudlick, pbonzini
Target Milestone: 4.4-3Keywords: Reopened
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:04:03 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: 913098    
Bug Blocks:    
Attachments:
Description Flags
screengrab
none
Screenshot of the status area none

Description Petr Šplíchal 2012-05-18 08:41:13 UTC 
Description of problem:

The "Mark as duplicate" field is displayed even when the status is
CLOSED/ERRATA, furthermore hitting it does not have any effect.

Version-Release number of selected component (if applicable):
3.6, 4.2

Steps to Reproduce:
https://partner-bugzilla.redhat.com/show_bug.cgi?id=227655
  
Actual results:
Status: CLOSED [ERRATA] of <empty input field>
Mark as duplicate

Expected results:
Status: CLOSED [ERRATA]
Comment 1 Simon Green 2012-05-18 11:56:04 UTC 
Created attachment 585393 [details]
screengrab
Comment 2 Simon Green 2012-05-18 11:57:43 UTC 
Seems fine to me, as per the attached screenshot. If you have javascript disabled, the section below the comment box will allow you to enter a duplicate bug number, but that is expected.
Comment 3 Petr Šplíchal 2012-05-21 06:35:21 UTC 
Created attachment 585740 [details]
Screenshot of the status area

That's strange, here's what I get when viewing that bug. I'm even
not able to update the status as it's just a plan text. I double
checked that I'm logged in.
Comment 4 Simon Green 2012-10-09 07:23:12 UTC 
*** Bug 652294 has been marked as a duplicate of this bug. ***
Comment 5 Paolo Bonzini 2012-10-16 15:04:36 UTC 
Yet another bug looking like this: bug 827163
Comment 7 Simon Green 2012-11-14 11:00:49 UTC 
*** Bug 875020 has been marked as a duplicate of this bug. ***
Comment 10 Simon Green 2012-12-17 03:00:53 UTC 
*** Bug 882165 has been marked as a duplicate of this bug. ***
Comment 11 Chen Chen 2013-02-17 08:50:58 UTC 
Verify version 4.4 on qe server --> FAIL

Verify steps:
1.Log in bugzilla with a public account.
2.Create a bug which product contained 'bugzilla'.
3.Change the bug status to CLOSED/ERRATA.
4.Chick Status of this bug at the bottom of the page.
  
Actual results:
Status: CLOSED [ERRATA]
Mark as duplicate

Expected results:
Status: CLOSED [ERRATA]
Comment 15 Chen Chen 2013-02-20 11:35:37 UTC 
simon: 

- Please ignore the comments 12 and 14. 

- I added a new bug 913098 to deal with the issue in comment 12.

- and I updated the Verify result:

Verify version 4.4-1 on test server --> Depend on bug 913098

Verify steps:
1.1. Login bugzilla with public.					                                --pass
1.2. Create a rhel6 bug, update the bug, and set bug status closed [errata]					--blocked by a new bug 913098
1.3. Refresh the bug page, check the status field under the page.						--not test
1.4. Update the bug's status and resolutions.									--not test
2.1. Login bugzilla with redhat. 									--pass
2.2. Create a rhel6 bug, set public as assignee.							--pass
2.3. Login bugzilla with public, then update the bug's status to closed [errata].			--blocked by a new bug 913098
2.4. Refresh the bug page, check the status field under the page.						--not test
2.5. Update the bug's status and resolutions.									--not test
3.1. Login bugzilla with redhat.									--pass
3.2. Create a rhel6 bug, set public as qa contact. 							--pass
3.3. Login bugzilla with public, then update the bug's status to closed [errata]. 			--pass
3.4. Refresh the bug page, check the status field under the page. 						--pass
3.5. Update the bug's status and resolutions.									--pass
4.1. Login bugzilla with public.									--pass
4.2. Search a rhel6 bug that public is not the reporter, assignee and qa contact of this bug.	--pass
4.3. Update the bug's status to closed [errata].								--pass
5.1. Login bugzilla with redhat.									--pass
5.2. Search a rhel6 bug and set the bug's status to closed [errata].						--pass
5.3. Refresh the bug page, check the status field under the page.						--pass
5.4. Update the bug's status and resolutions.									--pass
6.1. Login bugzilla with admin.									--pass
6.2. Search a rhel6 bug and set the bug's status to closed [errata].						--pass
6.3. Refresh the bug page, check the status field under the page.						--pass
6.4. Update the bug's status and resolutions.									--pass
  
Actual results:
see above.

Expected results:
1. After step 1.3, Status is only CLOSED [ERRATA] and there is no 'Mark as duplicate' and no 'of <empty input field>'
2. After step 1.4, bug status and resolution can not be changed.
3. After step 2.4, Status is only CLOSED [ERRATA] and there is no 'Mark as duplicate' and no 'of <empty input field>'
4. After step 2.5, bug status and resolution can not be changed.
5. After step 3.4, Status is only CLOSED [ERRATA] and there is no 'Mark as duplicate' and no 'of <empty input field>'
6. After step 3.5, bug status and resolution can not be changed.
7. After step 4.3, bug status can not be changed.
8. After step 5.3, Status is only CLOSED [ERRATA] and there is no 'Mark as duplicate' and no 'of <empty input field>'
9. After step 5.4, bug status and resolution can not be changed.
10. After step 6.3, Status is only CLOSED [ERRATA] and there is 'Mark as duplicate' link.
11. After step 6.4, admin account can update the bug's status and resolution.