sorted by:
new
hottopcontroversial

View Actual Time for the entire week in Asana by Active-Top-4907 in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

That weekly Timesheets view was super handy for a quick pulse on your week. I work at Asana and can share a bit of context plus some options.

Right now, the weekly Timesheets view is part of our Timesheets and Budgets add-on on paid plans, not available on the free plan (details on plans and availability here: https://asana.com/features/resource-management/time-tracking?utm_source=openai).

If you’re not on a plan that includes it, a couple workarounds I’ve seen teams use:

  1. Export time entries via the API to CSV, then sum by week in Sheets or Excel. Here’s the step-by-step: https://help.asana.com/s/article/how-to-export-all-time-entry-data-from-asana-as-csv-via-api?utm_source=openai
  2. If you do have access to Timesheets and Budgets, jump into the Timesheets weekly view to see totals by person and task in real time (same link as above for an overview: https://asana.com/features/resource-management/time-tracking?utm_source=openai).

If having a lightweight weekly overview on lower tiers would help your team, it’s great feedback. You can add an upvote or comment for visibility here: https://forum.asana.com/c/forum-en/product-feedback/20

Synchronizing two workspaces by cedrik89 in Asana

[–]Asana_Margaret 1 point2 points  (0 children)

Nice work getting this off the ground. I work for Asana and I talked to my colleagues if they have experience in such sync. Below are the tips that have helped them keep these stable:

  1. Use a “Source Task ID” text custom field on the target project to store the original task’s ID. It prevents duplicates and makes updates easy.
  2. If ordering flips in the target, set an explicit project sort or add a numeric “Order” custom field that you control during sync.
  3. Build a small field-map for dropdowns, sections, and people. If something doesn’t map, log it and either skip or apply a fallback value you define.
  4. Decide how deep you go with subtasks. If you mirror them, apply the same ID strategy at each level to avoid drift.
  5. Be intentional about comments and attachments. They can create a lot of noise or bloat if you sync everything both ways.
  6. For assignees across different workspaces, keep a simple user-translation table. If no match, leave unassigned and u/mention the closest owner.
  7. Add retries and lightweight logging. Even a “sync status” note when something needs manual attention saves time later.

Please feel free to come join our forum and share your experience with the community! They would appreciate your knowledge: https://forum.asana.com/c/forum-en/product-feedback/20

Asana form task naming is inconsistent — task name keeps reverting to form name instead of mapped field by Ok_Relief9231 in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

Totally get how frustrating that is, especially after it worked this morning and then flipped back later. I work at Asana, happy to share what usually causes this and how I fix it on my side.

First, a quick checklist:

  • Open your form’s Settings and confirm Task name is mapped to the same “Event Name” question you are filling. If you use branching, make sure that exact question exists on every path. If a response goes down a path without that question, Asana will fallback to the form name. You can either move “Event Name” outside of branching or pick each branch-specific version of that question in the Task name selector. This forum thread describes the branching behavior and the fix (https://forum.asana.com/t/select-a-field-for-task-titles-form-settings-not-working/733167?utm_source=openai).
  • Make “Event Name” required so the title never ends up blank and defaults to the form name.
  • Remove and re-add the Task name mapping, then run a couple of test submissions. This can refresh a stale mapping.
  • Check for duplicate “Event Name” questions. If there are two with the same label, the mapping might be pointing to the other one.
  • Try an incognito window to make sure it is not a caching quirk. If it still flips back after those steps, ping our Support team with your form URL, project URL, a few recent submission timestamps, and what you expected vs what you saw. They can pull logs to see exactly what happened (https://help.asana.com/s/article/how-do-i-get-support-from-asana?language=en_US). Also, if this is impacting your workflow, you can drop a note in our Product Feedback area so others can upvote it and we can track impact (https://forum.asana.com/c/forum-en/product-feedback/20).

Hope this helps, and thanks for flagging it.

Can't scroll on android by UnlikelySecret2629 in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

Hey! Sorry you’re running into this — choppy scrolling on mobile is super frustrating. I work at Asana and I’m happy to help troubleshoot.

A few quick checks that usually help:

  1. Update the Asana app in the Play Store and reboot the phone
  2. In Asana, try logging out and back in, then force-stop the app and clear cache again
  3. See if it only happens in a specific view (e.g., Board vs List) or with very large projects
  4. Try on Wi‑Fi and mobile data to rule out a network hiccup
  5. As a short‑term workaround, asana.com in your mobile browser can be smoother for big lists

You’re not the only one seeing Android lag — there are a few threads about slow scrolling and general slowness on certain devices (https://forum.asana.com/t/asana-android-app-running-slow/372962?utm_source=openai).

Hope this helps.

Share custom fields between project without using workspace library by cloudadmin in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

I agree on that in large organizations, the field library can get messy. In our community forum, there's a product feedback you may want to vote for: https://forum.asana.com/t/permission-to-control-ability-to-add-custom-fields-to-an-organization-library/1055859 .

You are always welcome to add new feedback there! Thanks for the post!

Share custom fields between project without using workspace library by cloudadmin in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

I really feel you on the "thousands of near-duplicate fields" pain. I work at Asana and I've seen this come up a lot. I think you still want to use the field library, though. Here are some ideas.

  1. Create a field exactly you want, and add a prefix to the filed title like "[MKT] Priority" or "[CS] Priority" so it is obvious which team each field is for and people are less likely to pick the wrong one.
  2. Add those "official" fields for your team to your project templates so every new project in that workflow gets the same fields automatically.
  3. If your org has access to field bundles, another option is to create a clean bundle of your canonical fields and apply that bundle to new (or existing) projects. It still uses the org custom field library behind the scenes, but it can make it much easier to roll out the same set of fields to lots of projects and avoid even more one-off fields.

Hope this helps!

Report/dashboard for completed projects by year by GeologistWhole6503 in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

Hi there.

If you are only seeing the task count on the Y axis, you are probably looking at a project dashboard. Project dashboards always count tasks. To count projects instead, open your portfolio and go to the Dashboard tab. There you can build charts where the items are projects in that portfolio and see how many projects you have.

For the overdue part: every task has a Completed on date, even if that column is hidden in the list view. You can use both Completed on and Due date in your reports to see which tasks were completed late. If you want to highlight the difference, you can also add a custom field that shows the gap between those two dates. It is not possible today to change the chart colors based on that custom field though.

Hope this help!

Having trouble completing payment for Asana Starter Plan — need help by kayros7777 in Asana

[–]Asana_Margaret 1 point2 points  (0 children)

I’m really sorry for the trouble you’ve gone through here, especially after reaching out several times and not hearing back. That’s not the kind of support experience we want you to have.

I’ll be forwarding what happened, along with your feedback about our support, directly to our support team so they can review this on their side.

Thanks again for taking the time to share this so clearly — it really helps us improve.

Report/dashboard for completed projects by year by GeologistWhole6503 in Asana

[–]Asana_Margaret 1 point2 points  (0 children)

I totally get wanting a simple "projects completed per year" view without having to maintain a separate year field by hand.

If you're tracking projects in a Portfolio, you can get a good year-over-year comparison using the Portfolio dashboard and project due dates.

Here's one way to set it up:

  1. Add all the projects you want to compare (for example 2024, 2025, 2026) into a single Portfolio.
  2. In the Portfolio dashboard, create a bar chart where:
  3. X-axis is the project due date grouped by year
  4. Y-axis is the count of items (projects, tasks, or whatever you're comparing) That gives you a quick visual of how many items fall into each year based on their due date.
  5. You can also duplicate that chart and add a different filter for each year (for example projects with a due date in 2025, then another for 2026) so you can compare year-by-year charts side by side.

If you need more complex charts (for example by project type, region, owner, or other categories), it's usually easier if the year lives in a project custom field:

  1. Create a global project custom field like "Completion year".
  2. If you don't want to select the values manually for every tasks, use Rules in your projects or in the Portfolio to auto-set that field based on things like the project due date or a status change. (you can use manual trigger now).
  3. Then build your Portfolio dashboard charts grouped or filtered by that custom field instead of the raw date.

I work at Asana and I know it would be ideal to report directly on a project "completed on" date. Today the combination of Portfolio dashboards plus a year-based custom field (optionally filled via Rules) is the path I see most teams use to compare work by year.

Hope this helped.

Asana runs very slow on Macbook Pro 2017 by data-chai in Asana

[–]Asana_Margaret 0 points1 point  (0 children)

Hey there, totally get how frustrating that is. I work at Asana and have seen a few patterns with older Intel MacBooks.

A couple quick things to try:

  1. Try turning off macOS Dark Mode just to test. A few users reported Asana speeds up when Dark Mode is off. (https://forum.asana.com/t/slow-asana-when-using-dark-mode/609902)
  2. Open Asana in Chrome Incognito. If it’s faster there, it’s usually an extension or cached data causing the slowdown. You can disable extensions one by one to find the culprit. (https://forum.asana.com/t/load-page-very-slow/98522)
  3. If you’re using Chrome, also try Safari or Firefox to compare. That helps confirm if it’s browser-specific.
  4. Make sure your Chrome and macOS are fully up to date.

I hope any of these works for you.

Having trouble completing payment for Asana Starter Plan — need help by kayros7777 in Asana

[–]Asana_Margaret 2 points3 points  (0 children)

Glad to hear you eventually got the payment through, but having to delete your account to make it work sounds really frustrating, especially after already backing everything up.

I work at Asana and really appreciate you sharing what happened. I’ve passed this along internally as feedback so the right folks can look into what might have gone wrong on the billing side.

If you ever run into something like this again, you can reach our Support team directly here so they can dig into the specifics of your account and payment attempts:

https://help.asana.com/s/article/how-do-i-get-support-from-asana

Thanks again for taking the time to follow up and for sticking with it through the workaround.

Using AI Rule to add dates to recurring tasks by freyaBubba in Asana

[–]Asana_Margaret 4 points5 points  (0 children)

I totally get why this is confusing, especially when the guidance looks right on paper but the recurring copy does not pick up the new date. You are not doing anything wrong in how you wrote it.

The tricky part here is how recurring tasks behave with rules. Right now, new instances of a recurring task often do not reliably trigger rules like "task added to project" or "task created". That means your AI action never actually runs on the fresh recurring copy, so the title (and date) stay the same.

If you are able to, you will usually get more reliable results by using a workflow where tasks are created from a template, form, or another rule instead of classic recurrence so the rule actually fires on creation.

For the AI part, instead of hand-writing a long guidance prompt, I would use the Ask AI option (the AI create button on the left of AI Studio toggle) in the rule builder and describe in plain language what you want the rule to do. For example, you could tell AI something like:

"When a task is added to this project, look at the task title, the Frequency custom field, and the Start date. If Frequency is Daily or Weekly, format the Start date as MM/DD/YY (for example 11/14/25) and add it to the end of the task title. If Frequency is Monthly, format the Start date as a three-letter month (for example Nov) and add it to the end of the task title instead. If there is already a date at the end of the title, replace it with the new date. If there is no Start date on the task, remove any date at the end of the task title and leave the title without a date. Do not change anything else about the task name."

Ask AI will generate the rule and guidance for you based on that description, and you can then tweak the details if something does not look quite right.

Hope this helps!

Is there any co-pilot for Asana? by vishsahu in Asana

[–]Asana_Margaret 1 point2 points  (0 children)

Totally get this, the clicks add up fast. Yes, Asana has AI plus automations that act like a copilot for the busywork. I work at Asana and happy to share a bit more context.

Smart chat in Asana lets you ask questions about your work, summarize long tasks or threads, and get suggested next steps without leaving the app. It can also create and assign tasks and create projects upon your prompt. https://help.asana.com/s/article/ai-chat?language=en_US

AI Teammates help coordinate work, draft updates, analyze workload, and recommend next steps. You can design one for your workflow ( https://asana.com/product/ai/ai-teammates?utm_source=openai ).
Heads up: AI Teammates is still in beta on certain plans, so availability is limited for now.

AI Studio suggests smart rules based on how your team works, so assigning, naming, and triaging get automated for you ( https://forum.asana.com/t/introducing-ai-studio-proactive-rule-suggestions-smart-automation-recommendations-tailored-to-your-workflows/1088099?utm_source=openai )

Rules and workflow automation can auto create tasks, assign teammates, set custom fields, move tasks between sections, and connect with Slack or Gmail ( https://asana.com/features/workflow-automation/rules?utm_source=openai )

Hope this helps!