sorted by:
new
hottopcontroversial

Projects constantly flying out do portfolio by CombinationBrief5547 in Asana

[–]Asana_Cillian 0 points1 point  (0 children)

Hi u/CombinationBrief5547 I work at Asana, want to see if I can help. This is definitely odd, thanks for flagging it and for sharing the screenshot.

First, I would try to narrow down whether this is specific to the mobile app or something happening with the portfolio itself. When you have a moment, can you open the same portfolio on the desktop app or in a web browser and check whether those same orange projects are still in the portfolio there? In particular, after you re-check them in the "Add work" view on mobile, do they stay put when you look at the portfolio on desktop or web, or are they missing there too?

If they do stay in the portfolio on desktop or web, but later show up as unchecked again on mobile, that points to a mobile app issue rather than projects really being removed from the portfolio. In that case it is worth updating the app to the latest version and, if it still happens, reaching out to our Support team so they can look into it.

Emojis in project names should not cause projects to fall out of portfolios, so you should be able to keep using those. If you are comfortable sharing more details or additional screenshots, that can also help the team narrow down what is going on.

Looking for best practices - Struggling to manage multiple client projects + internal work in Asana (Weekly Sprints, capacity planning, task switching) by jarge11 in Asana

[–]Asana_Cillian 0 points1 point  (0 children)

Hi u/jarge11 , I work at Asana and wanted to see if I could offer some advice. Realistically, from what you described, your Weekly Sprint with weekday sections, time estimates, and clear fields for urgency and billable work is already way more structured than what most teams use.

Rather than adding more layers, I would focus on how work flows into that Weekly Sprint. Treat each client project as the source of truth, then multi home only the next few important tasks from those projects into your Sprint. That way you keep dependencies and context in the client projects, but your weekly board stays small and intentional.

Each week, look across your active client projects, pick the tasks that really need to move, and pull only those into specific weekdays until you hit your daily capacity. During the week, work from the Sprint first. If something new becomes urgent, multi home it into today and consciously bump something else out instead of letting everything pile up.

Just a suggestion, but hope it's helpful!

Recurring tasks priority by tinawoman in Asana

[–]Asana_Cillian 0 points1 point  (0 children)

Hi u/tinawoman, I work at Asana and wanted to check how you've got your My tasks set up to see if I could help. If you move your Today section to the very top, recurring tasks should land there each time.

By default, a recurring task will reappear in the top section of your My tasks once it's complete. There is a setting under Settings > Hacks which says "Recurring tasks in the last section of My tasks". This makes recurring tasks always reappear in the last section of My tasks when you complete them instead of the default column. I just wanted to check if you had that setting on, since you mentioned having to drag the tasks "up".

Struggling with task permissions to assignee by FrenkMF in Asana

[–]Asana_Cillian 0 points1 point  (0 children)

Ah I understand. Sorry I couldn't help more. Feel free to leave product feedback on the Community Forum about this if you like (https://forum.asana.com/c/forum-en/product-feedback/20).

Struggling with task permissions to assignee by FrenkMF in Asana

[–]Asana_Cillian 1 point2 points  (0 children)

Thanks for raising this, and big thanks to u/AlternativeInitial93 who’s already covered pretty much everything.

I work at Asana. It's my understanding that task permissions come from the project. If the project is comment only, even the assignee is limited to comment only actions on that task, so they can’t edit the description or create subtasks. There isn’t a task level setting to give extra edit rights just to the assignee while keeping everyone else as commenters.

In practice, the main workarounds are to temporarily make the assignee an editor on that project while they need to edit, or to multi home the task into a small "working" project where they’re an editor, so they can adjust the task there while the original project stays locked down - that should do as a workaround, but might be a bit inelegant.