Asana, show me your BUTs 🍑

Community Forum English Tips and Tricks Forum Leaders tips
#22

Thanks @Christina_Davies, I feel like for now this is not a BUT but just a missing feature. Feel free to challenge.

#23

Today was my regular check, I believe the list is still correct, nothing to remove.

1 Like
#24

@Gerald_Thomas I created B6.9 and B6.10, does it make sense?

Also added B3.5 B8.1 B7.3 B7.4

1 Like
#25

Hi @Bastien_Siebman, I think :peach: B8.1 is no longer an issue (!)

1 Like
#26

I added :peach: B7.5 and :peach: B8.1 is indeed fixed! :muscle:

2 Likes
#27

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

#28

I understand. I don’t see it as a BUT but just a missing feature…

#29

Added 2 BUTs:

:peach: 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.

:peach: B9.1 A task audit trail will show an incoming mention BUT it won’t show future mentions if the source task was recurring.

2 Likes
#30

@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 :sweat_smile:
:link: Relevant topic.

#31

I’ll collect my brain on the floor and get back to you shortly :sweat_smile: :brain:

1 Like
#32

:exploding_head: :rofl:

#33

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?

#34

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.

#35

That seems like a very specific use case, I’ll put it aside for now if that’s ok with you.

1 Like