IT DID!
xref https://phabricator.wikimedia.org/T388022#11784455
Open Tasks
Tasks (15)
- Restricted Project
- Fri, Mar 27, 10:10 PM
- T176 testing for T397573
- Test-Workboard-Project-1
- Restricted Project
- Oct 22 2025, 12:06 PM
Assigned: a_smart_kitten__test - Sep 23 2025, 3:12 PM
Assigned: a_smart_kitten__test2- Sep 23 2025, 3:04 PM
Assigned: a_smart_kitten__test2- Sep 17 2025, 11:08 AM
Active Repositories
- No repositories found for this query.
Recent Activity
Sun, Apr 5
Sat, Apr 4
Thu, Apr 2
apparently not with conduit either, at least not with maniphest.edit:
damnit i forgot to change the visibility of the parent task back to hidden before trying this ://
[{"type":"parent","value":"PHID-TASK-rdnghrhopik2clze6aiv”},{"type":"title","value":"test subtask creation of a hidden task that i can't see but that i know the PHID of"}]or something like that i guess
wait what about conduit
turns out that they apparently can’t:
Parent task identifier "276" does not identify a visible task.
Sat, Mar 28
Fri, Mar 27
Tue, Mar 17
True, though that wouldn't restrict malicious actors from being able to edit via the API if they wanted to (as documented e.g. at https://we.phorge.it/book/phorge/article/forms/#use-case-security-issues:~:text=regardless%20of,Conduit%20API).
Mon, Mar 16
Another idea might be to restrict what forms you can use to edit. I think you could allow claiming a task that way while disallowing some other edits.
Sun, Mar 15
note to self: one thing is that this would appear to prevent non-members of Task-Editors from claiming tasks as well (which might in turn mean that new developers then couldn’t assign a task to themselves)
(this _test2 account is not currently in the #pseudo-trusted-contributors project)