Bug 2215165 - Add embargoed data category
Summary: Add embargoed data category
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-06-14 23:06 UTC by Jeff Fearn 🐞
Modified: 2023-07-03 00:17 UTC (History)
0 users

Fixed In Version: 5.0.4-rh88
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-03 00:17:37 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2212582 0 unspecified CLOSED Change Embargoed data category to "Security Restricted" 2023-07-03 00:17:37 UTC

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.


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