Page MenuHomePhabricator

Allow task statuses to "lock" them, preventing additional comments and interactions
ClosedPublic

Authored by epriestley on Mar 2 2017, 9:27 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Dec 18, 9:52 AM
Unknown Object (File)
Wed, Dec 18, 6:30 AM
Unknown Object (File)
Mon, Dec 16, 7:50 PM
Unknown Object (File)
Fri, Dec 13, 11:18 PM
Unknown Object (File)
Thu, Dec 12, 6:03 PM
Unknown Object (File)
Wed, Dec 4, 6:32 AM
Unknown Object (File)
Mon, Nov 25, 11:50 AM
Unknown Object (File)
Nov 21 2024, 10:52 AM
Subscribers
None

Details

Summary

Ref T12335. See that task for discussion. Here are the behavioral changes:

  • Statuses can be flagged with locked, which means that tasks in that status are locked to further discussion and interaction.
  • A new "CAN_INTERACT" permission facilitates this. For most objects, "CAN_INTERACT" is just the same as "CAN_VIEW".
  • For tasks, "CAN_INTERACT" is everyone if the status is a normal status, and no one if the status is a locked status.
  • If a user doesn't have "Interact" permission:
    • They can not submit the comment form.
    • The comment form is replaced with text indicating "This thing is locked.".
    • The "Edit" workflow prompts them.

This is a mixture of advisory and hard policy checks but sholuld represent a reasonable starting point.

Test Plan

Created a new "Locked" status, locked a task. Couldn't comment, saw lock warning, saw lock prompt on edit. Unlocked a task.

Diff Detail

Repository
rP Phabricator
Branch
interact2
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 15869
Build 21002: Run Core Tests
Build 21001: arc lint + arc unit

Event Timeline

Locked task:

Screen Shot 2017-03-02 at 1.30.04 PM.png (982×1 px, 122 KB)

Override prompt (requires edit permission):

Screen Shot 2017-03-02 at 1.30.47 PM.png (982×1 px, 127 KB)

Can we get the name of the object somehow? "This task has been locked"

I think it's going to get a little gross, but I'll see what I can do.

  • Specialize all the strings for the object type.
  • Replace the "subscribe" specialization for the extension with an object type specialization.
This revision is now accepted and ready to land.Mar 3 2017, 12:40 AM
This revision was automatically updated to reflect the committed changes.