Closed Bug 1457900 Opened 3 years ago Closed 2 years ago

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

Categories

(Conduit :: Phabricator, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: smacleod, Assigned: dkl)

Details

(Keywords: conduit-backlog, conduit-triaged)

Attachments

(1 file)

45 bytes, text/x-github-pull-request
Details | Review
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.
Keywords: conduit-triaged
Whiteboard: [phabricator-backlog]
Assignee: nobody → dkl
Status: NEW → ASSIGNED
See no reason for this to be private.
Group: conduit-security
Attached file github pr #606
Merged into master.
Status: ASSIGNED → RESOLVED
Closed: 2 years 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.