Apr 29 2020
Just a question - are there any technical reasons why providing custom field for "projects" may not be a good idea?
Feb 28 2020
@epriestley As perhaps an example of another use case, in my workplace we needed, amongst others, the following lists of Maniphest tasks:
- assigned to the viewer, regardless of the author,
- authored by the viewer, without self-assigned,
- subscribed by the viewer, without (1) and (2).
(1) is obviously trivial (there's already a built-in query), but the other two seemed to require custom "NOT" filtering. Of course, (2) can be solved to an extent by using "Group by assigned", but it's not very convenient. Because I tend to self-assign most of the tasks that I create, the ones that I have assigned to other people quickly get visually overwhelmed by the large group of "Assigned to kerberizer" (not to mention that with my username this huge group tends to get in the middle of the list).
Nov 21 2019
Nov 8 2019
Aug 22 2019
Jul 31 2019
This is likely straightforward.
See also PHI1358, which is an actual concrete request for sensible relabeling of "Description" in a subtype.
Jul 18 2019
Jul 17 2019
Trying to preserve markup format in the output is likely a road to mental ruin (Hyperlinking, referencing, bolding, formatting in who knows what export formats). PhabricatorStringExportField should be sufficient.
Mar 9 2019
I wholeheartedly agree that all that proxy field mess needs to go away. With that gone the only moderately confusing part remaining would be the way in which custom fields interact with herald, email and notifications.
Mar 1 2019
(This is likely to be very long, very rambling, and not particularly enlightening or useful.)
Feb 28 2019
Making a way to set fields to default: disabled would make this feature even better ;)
Feb 13 2019
Feb 11 2019
This would be incredibly useful for the things we are trying to do at WMF. I've gone so far as to duplicate lots of forms for each subtype and remove fields as needed. This results in N * N forms and it's not at all manageable beyond a very small number of sub-types.
Feb 8 2019
When we reach getCustomFieldSpecificationForRole($role), via EditEngine, the $this object currently does not have a subtype set, so it can't make any decisions about which fields to expose. This appears to have a fairly surgical fix in EditEngine, but if there are like 10 more of these coming it might merit another look.
Feb 1 2019
These have existed for a while and recently got support for customizing sub-object behaviors in 2018 Week 50 (Mid December) and are being extended to Projects in 2019 Week 5, so it looks like they're here to stay.
Jun 27 2018
PHI781 asks for [ ] Show on commit message template. for "Maniphest Tasks:".
Jun 12 2018
Jun 2 2018
From https://discourse.phabricator-community.org/t/how-to-get-custom-field-of-transactiontype/1532 (and my followup research), there doesn't appear to be a way to extract custom field information using conduit (or Herald Web Hooks).
transaction.search actually lists type as null and no fields.
Feb 16 2018
It would be perfect if the syntax supported in remarkup links could be used, which means that for @swisspol's example, projects/phabricator_transition/ would translate to https://temp.phacility.com/w/projects/phabricator_transition/.
And it would be even more awesome if the behavior of the displayed link in the "view" page could be the same, which means that in this case, it wouldn't display the link but the name of the Phriction page!
Jan 26 2018
Jan 23 2018
Jan 19 2018
I've marked D18879 as fixing this. It does not extend bulk editor support to all custom field types, but makes such support generally trivial. We'll fill in and test more field types as use cases arise.
Oct 4 2017
@epriestley so maybe this isn't the right place to leave this comment (let me know if I should create a new task?) but I'm finding this is acting in a way that seems a bit inconsistent. In particular, I added a new boolean custom field --
Aug 25 2017
I'm going to call this effectively resolved:
Aug 24 2017
Jul 26 2017
Seems better to pursue this as an CustomField extension. https://secure.phabricator.com/book/phabricator/article/custom_fields/
Jul 9 2017
Jun 27 2017
You can find tasks with no owner by searching for "No Owner", like this: