Asana does not communicate on their roadmap. My personal guess: they wonât, for 2 reasons: other 3rd party do it well, a tiny portion of users need it. (I donât work for Asana)
For T3. Rules: You can apply rules based on any custom field, or all custom fields, BUT not only certain custom fields: Need âContains onlyâ option for multi-select fields in Rules
Thanks @Christina_Davies, I feel like for now this is not a BUT but just a missing feature. Feel free to challenge.
Today was my regular check, I believe the list is still correct, nothing to remove.
I added B7.5 and
B8.1 is indeed fixed!
@Bastien_Siebman: My biggest BUT at the moment: No DEV-Team would ever like to use Asana without that feature: Code snippets in Asana - #280 by Albert_Reiner
Even as product owner, I miss that feature.
Tables in task descriptions are already announced. But I think code blocks are much more important, because then Asana gets relevant for a whole new target group.
I understand. I donât see it as a BUT but just a missing featureâŠ
Added 2 BUTs:
B2.4 A template allows to define due dates relative to project start or due date BUT a task converted to a project using a template in a rule will use the trigger date.
B9.1 A task audit trail will show an incoming mention BUT it wonât show future mentions if the source task was recurring.
@Bastien_Siebman , a suggestion for B4.2:
When you add custom fields to a Portfolio, you can âAdd or hide fieldsâ in the status update of all the projects that belong to that portfolio BUT if you add custom fields to a nested Portfolio, then these custom fields are not available in the âAdd or hide fieldsâ part of the Portfolioâs status update (in the portfolios âProgressâ tab). Tricky to summarise
Relevant topic.
Iâll collect my brain on the floor and get back to you shortly
If I re-phrase, a status update at the portfolio level wonât let you hide or show fields? whatâs the link with nested portfolios?
Correct, a status update of a portfolio (from its âProgressâ tab) cannot show/hide any custom fields.
The only way (that I know of) to add such custom fields to a portfolio is to nest that portfolio in a âmasterâ portfolio in which those custom fields are added to. So even by doing this, these fields cannot be shown/hidden in the status update of such portfolios that are nested within the master portfolio.
That seems like a very specific use case, Iâll put it aside for now if thatâs ok with you.
You can add text fields to your tasks BUT you canât search them! For example, I have a text field called PO#, but I canât use the search feature to find any individual POs.
Welcome, @AHP_Office,
You can search text fields. Have you tried Advanced Search > Add filter > Custom field?
Larry
I had attempted that, and I just did again. Using âContains the wordsâ did not work. However, I just now had success using âIs exactlyâ which is a little less convenient if I donât know the entire PO, but at least workable.