Bug 2223237 - Allow termination process to bypass sub-component restriction
Summary: Allow termination process to bypass sub-component restriction
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Extensions
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-17 01:16 UTC by Jeff Fearn 🐞
Modified: 2025-10-17 00:00 UTC (History)
0 users

Fixed In Version: 5.0.4-rh92
Clone Of:
Environment:
Last Closed: 2023-09-11 00:05:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeff Fearn 🐞 2023-07-17 01:16:04 UTC
Description of problem:

The termination process can be interrupted by the mandatory sub-component requirement. As the termination process is used for GDPR processing it cannot be prevented from functioning.

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

How reproducible:
Easy

Steps to Reproduce:
1. Find a bug that has a missing sub-component
2. Terminate a user in any role on the bug

Actual results:
An error is thrown and the process is halted.

Expected results:
The process completes.

Additional info:

Comment 2 Jeff Fearn 🐞 2023-09-04 03:56:31 UTC
On QA server.

1. Find a bug with a missing sub-component.

2. Terminate the assignee

The user is terminated and the bug has the assignee changed.

3. Try to update the bug in the UI.

The submit is interrupted with the sub-component is mandatory message.

4. Try and update the bug in the bulk update form.

"sub-component is mandatory" error is thrown.

5. Try and update the bug in the API

"sub-component is mandatory" error is thrown.

Comment 3 Jeff Fearn 🐞 2023-09-04 05:32:02 UTC
This fix has been deployed to stage Bugzilla for a short public testing phase.

https://bugzilla.stage.redhat.com

Comment 4 Jeff Fearn 🐞 2023-09-11 00:05:04 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.


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