Page MenuHomePhabricator

Custom FieldsProject
ActivePublic

Recent Activity

Apr 29 2020

seporaitis added a comment to T12220: New custom type field: Project Tags.

Just a question - are there any technical reasons why providing custom field for "projects" may not be a good idea?

Apr 29 2020, 3:36 PM · Custom Fields, Feature Request

Feb 28 2020

kerberizer added a comment to T4444: "NOT" filter for all applicable lines in a Query.

@epriestley As perhaps an example of another use case, in my workplace we needed, amongst others, the following lists of Maniphest tasks:

  1. assigned to the viewer, regardless of the author,
  2. authored by the viewer, without self-assigned,
  3. 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).

Feb 28 2020, 9:51 AM · Maniphest, Custom Fields, Projects

Nov 21 2019

epriestley removed a parent task for T3794: Rebuild Diffusion/Audit on top of CustomField infrastructure: T4211: Commits only appear in tasks if they have "Ref T1234" and not "Maniphest Tasks: T1234".
Nov 21 2019, 4:06 PM · Restricted Project, Diffusion, Custom Fields

Nov 8 2019

epriestley added a subtask for T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes: T13449: When objects are created with a particular subtype, apply subtype-appropriate validation rules.
Nov 8 2019, 12:57 AM · Custom Fields, Maniphest

Aug 22 2019

epriestley closed T13384: When a custom field is "disabled", that should take precedence over the field being "required" as Resolved by committing rPc4399313737b: Respect "disabled" custom field status granted by "subtype" configuration in….
Aug 22 2019, 1:03 AM · Custom Fields
epriestley added a revision to T13384: When a custom field is "disabled", that should take precedence over the field being "required": D20726: Respect "disabled" custom field status granted by "subtype" configuration in form validation.
Aug 22 2019, 1:02 AM · Custom Fields
epriestley updated the task description for T13384: When a custom field is "disabled", that should take precedence over the field being "required".
Aug 22 2019, 12:52 AM · Custom Fields
epriestley updated the task description for T13384: When a custom field is "disabled", that should take precedence over the field being "required".
Aug 22 2019, 12:47 AM · Custom Fields
epriestley triaged T13384: When a custom field is "disabled", that should take precedence over the field being "required" as Normal priority.
Aug 22 2019, 12:47 AM · Custom Fields

Jul 31 2019

epriestley closed T13356: Support a "limit" configuration option for tokenizer-based custom fields as Resolved by committing rPb81c8380fb97: Document support for "limit" in tokenizer-based Custom Fields.
Jul 31 2019, 8:13 PM · Custom Fields
epriestley closed T13355: Support editing "date" custom fields via Conduit as Resolved by committing rP8e263a2f6482: Support "date" custom fields in "*.edit" endpoints.
Jul 31 2019, 8:10 PM · Custom Fields, Conduit
epriestley added a revision to T13356: Support a "limit" configuration option for tokenizer-based custom fields: D20691: Document support for "limit" in tokenizer-based Custom Fields.
Jul 31 2019, 8:02 PM · Custom Fields
epriestley added a comment to T13356: Support a "limit" configuration option for tokenizer-based custom fields.

This is likely straightforward.

Jul 31 2019, 7:55 PM · Custom Fields
epriestley triaged T13356: Support a "limit" configuration option for tokenizer-based custom fields as Low priority.
Jul 31 2019, 7:51 PM · Custom Fields
epriestley added a revision to T13355: Support editing "date" custom fields via Conduit: D20690: Support "date" custom fields in "*.edit" endpoints.
Jul 31 2019, 7:48 PM · Custom Fields, Conduit
epriestley triaged T13355: Support editing "date" custom fields via Conduit as Low priority.
Jul 31 2019, 7:38 PM · Custom Fields, Conduit
epriestley added a comment to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.

See also PHI1358, which is an actual concrete request for sensible relabeling of "Description" in a subtype.

Jul 31 2019, 7:32 PM · Custom Fields, Maniphest

Jul 18 2019

epriestley closed T13342: Support export of "date" and "remarkup" custom fields as Resolved by committing rP9ab5f59ca23c: Export "date" and "remarkup" custom fields to Excel + "zip" extension check.
Jul 18 2019, 4:59 PM · Custom Fields, Data Exporters

Jul 17 2019

aeiser added a comment to T13342: Support export of "date" and "remarkup" custom fields.

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.

Jul 17 2019, 11:26 PM · Custom Fields, Data Exporters
epriestley added a revision to T13342: Support export of "date" and "remarkup" custom fields: D20658: Export "date" and "remarkup" custom fields to Excel + "zip" extension check.
Jul 17 2019, 10:57 PM · Custom Fields, Data Exporters
epriestley triaged T13342: Support export of "date" and "remarkup" custom fields as Normal priority.
Jul 17 2019, 4:40 PM · Custom Fields, Data Exporters

Mar 9 2019

20after4 added a comment to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.

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 9 2019, 12:48 PM · Custom Fields, Maniphest

Mar 1 2019

epriestley added a comment to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.

(This is likely to be very long, very rambling, and not particularly enlightening or useful.)

Mar 1 2019, 4:55 PM · Custom Fields, Maniphest

Feb 28 2019

20after4 added a comment to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.

Making a way to set fields to default: disabled would make this feature even better ;)

Feb 28 2019, 9:27 PM · Custom Fields, Maniphest

Feb 13 2019

epriestley updated the task description for T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.
Feb 13 2019, 5:20 PM · Custom Fields, Maniphest
epriestley added a revision to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes: D20161: Add basic, rough support for changing field behavior based on object subtype.
Feb 13 2019, 5:19 PM · Custom Fields, Maniphest

Feb 11 2019

20after4 added a comment to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.

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 11 2019, 10:37 PM · Custom Fields, Maniphest

Feb 8 2019

epriestley added a comment to T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.

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 8 2019, 4:36 PM · Custom Fields, Maniphest
epriestley renamed T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes from Support enabling and disabling custom fields based on object subtypes to Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes.
Feb 8 2019, 3:59 PM · Custom Fields, Maniphest
epriestley triaged T13248: Support enabling and disabling (and making other adjustments to) custom fields based on object subtypes as Normal priority.
Feb 8 2019, 3:58 PM · Custom Fields, Maniphest

Feb 1 2019

epriestley closed T12314: Support formal task subtypes (like "bug" vs "feature") as Resolved.

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.

Feb 1 2019, 10:43 PM · EditEngine, Maniphest, Custom Fields, Feature Request

Jun 27 2018

epriestley added a comment to T6030: Allow CustomFields to specify additional options (like "required") configurable in `<application>.fields`.

PHI781 asks for [ ] Show on commit message template. for "Maniphest Tasks:".

Jun 27 2018, 3:57 PM · Restricted Project, Restricted Project, Custom Fields

Jun 12 2018

epriestley added a revision to T12314: Support formal task subtypes (like "bug" vs "feature"): D19490: Allow object subtypes to be changed via bulk editor.
Jun 12 2018, 5:25 PM · EditEngine, Maniphest, Custom Fields, Feature Request

Jun 2 2018

avivey added a comment to T418: Integrate CustomField into more interfaces.

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.

Jun 2 2018, 6:12 PM · Restricted Project, Restricted Project, Restricted Project, Maniphest, Custom Fields

Feb 16 2018

mcorteel added a comment to T8824: Allow relative URLs in custom fields of type "link".

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!

Feb 16 2018, 2:47 PM · Custom Fields

Jan 26 2018

epriestley closed T5954: Modularize "Export to Excel" as a feature of ApplicationSearch as Resolved.

I'm rolling this forward into T13049. See also D18919.

Jan 26 2018, 4:59 PM · Custom Fields, ApplicationSearch

Jan 23 2018

epriestley added a revision to T5954: Modularize "Export to Excel" as a feature of ApplicationSearch: D18919: Add a basic, general-purpose export workflow for all objects with SearchEngine support.
Jan 23 2018, 6:10 PM · Custom Fields, ApplicationSearch

Jan 19 2018

epriestley closed T5689: Batch edit of Maniphest custom fields as Resolved by committing rPae1b07bcfb43: Support "<select />" custom fields in bulk editor.
Jan 19 2018, 9:18 PM · Custom Fields, Maniphest
epriestley added a comment to T5689: Batch edit of Maniphest custom fields.

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.

Jan 19 2018, 3:02 PM · Custom Fields, Maniphest
epriestley added a revision to T5689: Batch edit of Maniphest custom fields: D18879: Support "<select />" custom fields in bulk editor.
Jan 19 2018, 2:59 PM · Custom Fields, Maniphest

Oct 4 2017

epriestley updated subscribers of T5016: Allow Herald rules for Maniphest to act on custom task fields.

The best place for this kind of question is now your organization's support pact -- @tammybutow or @alexmv should be able to help you get access.

Oct 4 2017, 11:34 PM · Herald, Custom Fields
ahoffer2 added a comment to T5016: Allow Herald rules for Maniphest to act on custom task fields.

@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 --

Oct 4 2017, 9:24 PM · Herald, Custom Fields

Aug 25 2017

epriestley closed T5873: Update Conduit for ApplicationTransactions, CustomFields and Edges as Resolved.

I'm going to call this effectively resolved:

Aug 25 2017, 2:30 PM · Haskell.org, Restricted Project, Restricted Project, ApplicationEditor, FreeBSD, Restricted Project, User Delight, Phacility, Custom Fields, Transactions, Conduit

Aug 24 2017

epriestley added a revision to T5873: Update Conduit for ApplicationTransactions, CustomFields and Edges: D18469: Provide some more detailed information about inline comments in "transaction.search".
Aug 24 2017, 10:19 PM · Haskell.org, Restricted Project, Restricted Project, ApplicationEditor, FreeBSD, Restricted Project, User Delight, Phacility, Custom Fields, Transactions, Conduit
epriestley added a revision to T5873: Update Conduit for ApplicationTransactions, CustomFields and Edges: D18467: Allow ModularTransactions to opt in to providing data to Conduit.
Aug 24 2017, 9:51 PM · Haskell.org, Restricted Project, Restricted Project, ApplicationEditor, FreeBSD, Restricted Project, User Delight, Phacility, Custom Fields, Transactions, Conduit
epriestley added a revision to T5873: Update Conduit for ApplicationTransactions, CustomFields and Edges: D18466: Add the skeleton for a "transaction.search" Conduit API method.
Aug 24 2017, 9:20 PM · Haskell.org, Restricted Project, Restricted Project, ApplicationEditor, FreeBSD, Restricted Project, User Delight, Phacility, Custom Fields, Transactions, Conduit

Jul 26 2017

chad closed T7591: Support computed "impact" and "leverage" fields on tickets as Wontfix.

Seems better to pursue this as an CustomField extension. https://secure.phabricator.com/book/phabricator/article/custom_fields/

Jul 26 2017, 8:47 PM · Custom Fields, Maniphest

Jul 9 2017

chad removed the image for Custom Fields.
Jul 9 2017, 7:29 PM

Jun 27 2017

epriestley added a comment to T4444: "NOT" filter for all applicable lines in a Query.

You can find tasks with no owner by searching for "No Owner", like this:

Jun 27 2017, 11:50 AM · Maniphest, Custom Fields, Projects
earthian added a comment to T4444: "NOT" filter for all applicable lines in a Query.

This is something that is needed every day, e.g. find tickets which are not yet assigned..

Jun 27 2017, 10:57 AM · Maniphest, Custom Fields, Projects