Asana, show me your BUTs 🍑

[Phil_Seeman]

Maybe edit them to be in strikethrough font?

[Bastien_Siebman]

@Phil_Seeman they are, aren’t they?

[Phil_Seeman]

@Bastien_Siebman

they are, aren’t they?

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

[Bastien_Siebman]

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.

[Bastien_Siebman]

I added

B2.6 A project has Saved Views but a template can’t define them.
B2.7 A project has a “Hide” button to define fields displayed but a template doesn’t have it.

Thanks @Kelsea_Lopez

[Rebekah_Chalkley]

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

@Rebekah_Chalkley

I can’t edit a rule that my teammate created, even though she has confirmed that the box is unchecked for “Only you can edit this rule.”

@Rebekah_Chalkley

Looking into this further, it looks like there’s a consistent pattern where all the rules I can’t edit are ones that have a “Slack - Send channel message” component in the “Do this” section.

I wonder if this is something for the Asana BUTs. Asana, show me your BUTs - #46 by Phil_Seeman

B3.7 You can edit a rule that someone else created (provided the box is unchecked for “Only you can edit this rule”), BUT not if one of the “do this” parameters is to push a message to Slack.

[Bastien_Siebman]

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

B1.1 Portfolios supports 1500 projects BUT Workload gets disabled about 250** → this is now 1500 projects in Workload

B5.4 Subtasks seem to be part of a project BUT project does not show up in My Tasks → they now do!

B5.5 List view supports subtasks BUT subtask drop-downs disappear when list is sorted or filtered. → it appears

B7.4 Audit logs are added to tasks BUT a user can remove some of them. → users can’t remove audit logs anymore

[Elyse_Restrepo]

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.

[Ka_Nishiyama]

I think it’s this link.

---

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

Undo actions

Is there a way to undo your last action? ie. undo task creation

---

B2.6 A project has Saved Views but a template can’t define them.

Saved view tabs to be supported in Project templates

Saved view tabs are awesome. But, currently, they cannot be setup within a project template so that they are predefined for a project that is created based on that project template. Currently, you need to set up view tabs manually each time, or as a workaround, duplicate a regular project, which unfortunately loses out on all the functionality of Project templates. Please add support for saved view tabs in Project templates PS: this would require Filter, Sort and Hide buttons available…

[Alejandro_J_Ortiz]

@Bastien_Siebman

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.

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:

The resulting project (in portfolio list view):

[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:

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!

[Richard_Sather]

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

[Alejandro_J_Ortiz]

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

[Richard_Sather]

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

[Bastien_Siebman]

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

Thanks @lpb for the nudge

[Bastien_Siebman]

I believe those are now fixed

B2.7 A project has a “Hide” button to define fields displayed but a template doesn’t have it.
B6.7 Tasks in a search result can be sorted by Project BUT not in a project with multi-homed tasks.
B6.8 Timeline has a conflict avoidance system when a due date is moved to the future BUT nothing happens when a task is moved back in the past.

[Bastien_Siebman]

Added
B6.12 “Tags” not syncing with Google Sheets, but exporting in Excel

[Bastien_Siebman]

Added
B3.7 A rule can trigger another rule but not trigger itself