Bug 2040108

Summary: bulk edit form missing close as duplicate
Product: [Community] Bugzilla Reporter: Jeff Fearn 🐞 <jfearn>
Component: Creating/Changing BugsAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Fearn 🐞 <jfearn>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-09 00:14:59 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:

Description Jeff Fearn 🐞 2022-01-13 00:19:12 UTC
Description of problem:
On the bulk edit form when marking bugs CLOSED DUPLICATE the 
dup_id field is missing.

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

How reproducible:
Always

Steps to Reproduce:
1. run a search
2. select some bugs
3. click edit
4. Change status to CLOSED
5. Change resolution to DUPLICATE
6. Try and set the bug id of the duplicated bug

Actual results:
You can't.

Expected results:
You can.

Additional info:
Make sure status, resolution and dup_id are next to each other.

Comment 1 Jeff Fearn 🐞 2022-01-13 00:58:36 UTC
NOTE: Any attempt to set more than one bug a sa duplicate will be rejected by the server. This needs to be obvious in the UI, maybe a message about it and disabling selecting the DUPLICATE resolution if more than one bug is selected.

Comment 2 Jeff Fearn 🐞 2022-04-28 05:04:40 UTC
On QA server:

1 generate a bug list
2 select some rows
3 select Edit
4 click 'Mark as Duplicate' checkbox
5 enter a bug id in to the revealed input
6 click Submit

Submission fails due to server side restriction on closing multiple bugs as dupes.

7 select 1 bug on list
8 repeat rest of submission

Selected bug is correctly closed as a duplicate.

Comment 3 Jeff Fearn 🐞 2022-05-05 00:10:46 UTC
The fix for this bug has been deployed to the stage server for public testing.

https://bugzilla.stage.redhat.com/

Comment 4 Jeff Fearn 🐞 2022-05-09 00:14:59 UTC
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.