How can I retroactively make a Red Hat bug private?

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

Context

I checked the box during submission in GNOME Abrt:

However, it’s not private! ^[1] Do I also need to check its duplicate?

---

1. bugzilla.redhat.com/show_bug.cgi?id=2369810#c14 ↩︎

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

It appears so:

--- Running report_Bugzilla ---
Checking for duplicates
Creating a new bug...
Failed to create bug.
Server says: 401 Unauthorized
{"code":113,"message":"Sorry, but you are not allowed to (un)mark comments or attachments as private.","error":true,"documentation":"https://bugzilla.redhat.com/docs/en/html/api/index.html"}
('report_Bugzilla' exited with 1)

Does that mean that the report-specific checkbox is inoperative? If so, I’ll report this to GitHub or RHBZ.

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

Not merely does that checkbox apparently not operate, but disabling its duplicate created a new bug, ^[1] rather than attaching to its apparent duplicate, which, presumably, means I just can’t even file a bug restricted!

Additionally, I see no option to in the BZ GUI anymore, so I’ll NEEDINFO the assignee.

---

1. bugzilla.redhat.com/show_bug.cgi?id=2369817#c13 ↩︎

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

@rokejulianlockhart

I’ll report this to GitHub

[Bug] The report-specific security restriction checkbox does not function.

[leigh123linux (Leigh Scott)]

Do user have the rights to mark issues private in the bug report?

normally you just set groups to ‘private’

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

@leigh123linux, thanks! That works: