When restricting a revision to a bugzilla group we should tag the revision with the project

RESOLVED FIXED

Status

RESOLVED FIXED
10 months ago
17 days ago

People

(Reporter: smacleod, Assigned: dkl)

Tracking

({conduit-backlog, conduit-triaged})

Details

Attachments

(1 attachment)

(Reporter)

Description

10 months ago
Right now when a revision is locked down to members of a project (representing a bugzilla security group) a custom policy is used for the revision. It's hard to inspect what exactly this custom policy does (you must edit the revision, click to change the policy, then re-click custom policy and the details are shown in the editor).

We should add the bmo-* project as a tag to the revision as well to make it more obvious what is going on.

Updated

10 months ago
Keywords: conduit-triaged
Whiteboard: [phabricator-backlog]
(Assignee)

Updated

9 months ago
Assignee: nobody → dkl
Status: NEW → ASSIGNED
(Assignee)

Comment 1

8 months ago
See no reason for this to be private.
Group: conduit-security
(Assignee)

Comment 2

8 months ago
Created attachment 8986267 [details] [review]
github pr #606
(Assignee)

Comment 3

7 months ago
Merged into master.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → FIXED
Keywords: conduit-backlog
Whiteboard: [phabricator-backlog]
You need to log in before you can comment on or make changes to this bug.