Bug 2215165

Summary:	Add embargoed data category
Product:	[Community] Bugzilla	Reporter:	Jeff Fearn 🐞 <jfearn>
Component:	Extensions	Assignee:	Jeff Fearn 🐞 <jfearn>
Extensions sub component:	RedHat	QA Contact:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	unspecified
Version:	5.0
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.0.4-rh88	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-03 00:17:37 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 🐞 2023-06-14 23:06:33 UTC

Description of problem:
Bug 2212582 changed the "embargoed" data category to "security restricted", now we need to add an embargoed category.

Add a field for setting a bug as embargoed. Restrict use of the field to the product security team.

Update the data category code to check this field.

Comment 2 Jeff Fearn 🐞 2023-06-28 04:35:08 UTC

On QA server.

1. Check FAQ for "Data Categories"

Embargoed has been added.

2. Set the Embargoed field on a bug.

The field ACLs are correct.

The data category banner on the page has 'Embargoed'.

Bug lists have the 'Embargoed' tag.

Searching for Embargoed works. $server/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&f1=cf_embargoed&o1=isnotempty&query_format=advanced

Comment 3 Jeff Fearn 🐞 2023-06-28 23:01:36 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-07-03 00:17:37 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.