Broadly, DifferentialCustomField drives a very large amount of stuff in Differential. This was the first generation of custom fields, and is the most complex implementation.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 16 2016
Dec 15 2016
Dec 14 2016
Dec 13 2016
Nov 29 2016
Nov 14 2016
in which folder we need to place maniphest.custom-field-definitions
Sep 12 2016
Sep 6 2016
Sep 3 2016
I tried to rephrase slightly to clarify the root cause rather than looking for a solution.
Aug 10 2016
I'd be more comfortable just saving the description if we didn't have CustomFields. I think we do something similar in Phriction today.
Aug 9 2016
Aug 8 2016
it's just likely very complex when we have to save an entire object state ... instead of approximately a single blob of text
Understood. For me personally, the single blob text would be more than sufficient. I don't mind repopulating everything else (assignment, subscribers, tags, customs, etc.) as those usually require much less thought and drafting.
Aug 7 2016
Jul 23 2016
(T11357 is a companion issue for Files.)
Jul 21 2016
Excellent! Thanks for this so very detailed answer. I will try the way of the phid.lookup to work this issue around in the while.
Jul 4 2016
Jul 2 2016
Jun 17 2016
We discussed this briefly out-of-band, but the draft part of this is probably only sensible as "soft" prioritization:
Jun 14 2016
Jun 8 2016
Jun 1 2016
We have all the information we need, I don't have suggestions for workarounds. This isn't on any immediate roadmap. See Planning for how we prioritize requests.
@chad Just want to follow up, does my latest comment explain my use case? is there any recommended workaround or future change that could help me with that?
May 24 2016
I see. Thanks chad.
May 23 2016
Generally, we want to understand problems, which is why I linked the guide to you. A example might be that Team A is "Marketing" and Team B is "Engineering" and the Field is a Select, that uses values X, Y, and Z, and Engineering triages them, but Marketing doesn't need to set them. This tells us a good story at which to understand overarching needs. Upcoming tools like Nuance sit in front of Maniphest and might be what you're looking for, or maybe not, I just don't have enough backstory here.
Sorry, I understood perfectly the feature you wanted. I don't understand the core problem you're trying to solve. If you could get into specifics, it would help us better understand if, for instance, you should just be using Nuance. Can you be more specific and tell us what the field your attempting to us is, for example?
@chad Sorry that I didn't explain that clear enough in the description, here is what I'm trying to accomplish:
May 20 2016
Can you tell us what you're specifically trying to accomplish? As requested I don't know what problem this solves.. See Contributing Feature Requests for more information.