Revisions and Commits
|Resolved||None||T6787 Clarify UI for Objects with a non-default Policy|
|Resolved||None||T5135 Allow to change defaults for Passphrase "Visible To" and "Editable By" policies|
|Duplicate||None||T6860 Allow creation of parameterized application policies|
|Resolved||epriestley||T4100 Support query parameterization in typeaheads|
|Resolved||None||T4420 Modernize typeahead datasources|
|Restricted Maniphest Task|
|Resolved||epriestley||T5750 Implement typeahead browse mode|
|Resolved||epriestley||T7688 Move token rendering into TypeaheadDatasource|
|Resolved||epriestley||T7689 Load handles just-in-time|
|Wontfix||epriestley||T7803 Implement a composite query which unifies cursor paging across subqueries|
|Resolved||epriestley||T5681 Allow applications to provide custom policy rules|
This is somewhat involved because there's no way to express the current defaults ("the viewing user") in an administrative policy control. That is, if you are "alincoln", you can set "Default View Policy" to "only alincoln can see this", but you can not select "only whichever user account is creating the credential can see this", so that when you create a credential the defaults are "only alincoln can see this", but when "htaft" creates a credential the defaults are "only htaft can see this".
This is not too difficult to fix, but not trivial.
It seems increasingly clear that T6860 was a really bad idea. New pathway forward here is completely straightforward:
- Start saving authorPHID on credentials.
- Add a "Credential Author" object policy for these objects, which looks like ManiphestTaskAuthorPolicyRule.
- Set that as the default policy.
- Expose standard policy default preferences.