Asana, show me your BUTs šŸ‘

Maybe edit them to be in strikethrough font?

1 Like

@Phil_Seeman they are, arenā€™t they?

1 Like

Yeah, they are now - they werenā€™t when I looked before - screen refresh/cache issue in my browser, I guess.

1 Like

fyi I was able to share this post with Asanaā€™s Product team and they were very interested, they are going to deep dive and compare the content with what is on the roadmap.

1 Like

I added

:peach: B2.6 A project has Saved Views but a template canā€™t define them.
:peach: B2.7 A project has a ā€œHideā€ button to define fields displayed but a template doesnā€™t have it.

Thanks @Kelsea_Lopez

5 Likes

Not sure if thereā€™s a standard method for requesting new things to be added, but I have a submission from my post here.

1 Like

Thanks to my awesome colleague Nico, I was able to strikethrough 4 BUTs that were fixed!

:peach: B1.1 Portfolios supports 1500 projects BUT Workload gets disabled about 250** ā†’ this is now 1500 projects in Workload

:peach: B5.4 Subtasks seem to be part of a project BUT project does not show up in My Tasks ā†’ they now do!

:peach: B5.5 List view supports subtasks BUT subtask drop-downs disappear when list is sorted or filtered. ā†’ it appears :slight_smile:

:peach:B7.4 Audit logs are added to tasks BUT a user can remove some of them. ā†’ users canā€™t remove audit logs anymore

4 Likes

The Notes tab is great, and the templates are helpful BUT there is a limit to the amount that the Notes tab holds which makes saving running notes for projects difficult to store/maintain.

I think itā€™s this link.


B7.3 Some actions can be undone BUT if you miss the popup, you canā€™t undo anymore.


B2.6 A project has Saved Views but a template canā€™t define them.

1 Like

Nice topic BTW!

This one caught my eye.
We use a workflow on a ā€œrequest & assignmentā€ type of project where we use a rule to convert tasks to projects (from template). Weā€™ve created hundreds of projects this way.
In my results, the project start date is taken from that converted taskā€™s START date. The resulting project end date is a result of the (relative) due dates of the rest of the tasks in the template, and will simply take the resulting LAST taskā€™s due date. (not the original converted taskā€™s due date).
[I wrote more on this on a previous post HERE}

Example:
(converted) task in the requests project:
image

The resulting project (in portfolio list view):
image
[Note the start dates are the same: Task = Project, However the project end date is different, becauseā€¦]

[ā€¦]This is the last task in the project, after it was created from the templateā€™s relative dates:
image

I guess if said task does not contain a Start date (only DUE date) the rule/project will default to the trigger/creation date?

So, for those leveraging the RULE to convert tasks to projects from templates and expect that the resulting project has relevant Start and End/Due Dates, Iā€™d recommend:

  • Make sure your originating task (to be converted) has a START DATE, not just a Due Date.
  • Make sure your template has AT LEAST a due date on your usual last task/milestone relative to the first task (such as ā€œproject completeā€, or ā€œcustomer-sign-offā€, or ā€œfinal invoice paidā€ etc). Ideally youā€™d have a pretty good handle on your typical project delivery workflow that you could have a baseline schedule/timeline for the critical path tasks; especially milestonesā€¦
  • Also, not a bad idea to default all projects created from this rule/template to a specific portfolio with a curated view with the Global Custom fields that it inherits from the converted taskā€¦

OK thatā€™s my $0.02, and thanks to @Bastien_Siebman and the rest of the forum leaders for this content! :slight_smile:

2 Likes

Hi @A.Ortiz , I would just add to your notes that the result of the rule action 'convert task to project (based on a template) will be affected by the templateā€™s ā€˜Due date ruleā€™, i.e. whether it is set After project start date or Before project due date.

Either setting will be affected by the original taskā€™s start or due date, respectively.
In your case is sounds like your template is set to ā€˜After project start dateā€™. That is why your projectā€™s due date is not the same as your taskā€™s due date, but instead their start dates are the same.

1 Like

@Richard_Sather Good observation!
However the second image selection, I understand only appears when creating from templates directly. Correct?

I donā€™t believe thatā€™s is the case (or at least I am not aware) if thereā€™s an option to make that choice when converting a task to a project from a rule, which is the more specific case I was referring to :wink: (If there is, Iā€™d like to know!)

That being said, I have not tried specifying Tasksā€™ due dates relative to the Project due Date (ā€œ## days before due dateā€) in the template and THEN creating the project by converting from a task via a rule actionā€¦ hmmmā€¦ time to experiment later!

Hi @A.Ortiz , the 2nd screenshot is what you will see when you click on the items of the 1st screenshot.

These are both taken within the project template editor, so this setting is ā€˜embeddedā€™ within the project template. Therefore when the template is used with a rule to convert task to a project, these settings are relevant and respected by the rule, as I explained above :wink:

Added :peach: B2.8 Custom fields can be pre-filled in project templates BUT not Date fields.

Thanks @lpb for the nudge

2 Likes