**Read me first** How you can give feedback and what we do next


Submit and vote on Asana product feedback. See details below for how your votes will impact Asana’s product roadmap. While Asana is unable to guarantee each request, we do take each request into consideration and thank you for your feedback.

How we’re listening to your product feedback.

We have been pleasantly surprised by the amount of organic product feedback you have submitted here in the Community. Many of you have asked what happens with the feedback after you submit it and we’re here to tell you! First and foremost, please know that we see your feedback and we are taking it into account. That said, as indicated in the category description, we cannot make any guarantees. Also, please be advised that feedback threads that are 6 months or older may be closed in order to keep the Community healthy and organized for all visitors. We will ensure that our product team is aware of the feedback before a thread is closed.

Voting for product features

This category is a place for you to provide feedback about the Asana product and vote on your favorite feature requests. Please vote on the ideas that you’d like to see implemented. Note that we will read comments to help us understand the context of your requests, but we will specifically use votes to prioritize your feature requests. Vote by clicking the “vote” button at the top left of each thread.

How your votes will impact Asana’s product roadmap

Your votes will help us understand the Community’s preferences as we bring Community feedback to our roadmapping discussions. These Community preferences will be integrated into Asana’s Voice of Customer process. What we’ll do is count your votes and analyze your feedback in the community, then cross reference it with the feedback our other teams are getting. Then we prioritize all requests against many factors including company vision, business needs, and so on.

We do not share a product roadmap because we are unable to promise a timeline and we want to ensure that the features and updates we release are as well made as possible. We wouldn’t want to release a sub-par feature just to meet a deadline - quality is super important to us. So, while we can’t promise a timeline or specific features, we can promise that we take your feedback seriously and we are considering it alongside other customer feedback at Asana.

So, will your idea be put into our product roadmap?

Maybe! We do our best to prioritize what is important to all customers and create features that will have the greatest impact on the customer experience. This means that while we may not implement the exact feature you request, we will try to create features that address the pain point or problem you’re trying to solve.

Background on how we build our product roadmap at Asana

Jackie Bavaro, the head of Product at Asana, wrote a Medium article describing how we build our product roadmap at Asana. Read the ins and outs of how we build our product roadmap in Jackie’s article here:



One of our most important processes is “Voice of the Customer”, or VoC. Each customer facing and business team works with all of the individual people to create their own top-10 list of product requests. For example, the customer support team considers the number of tickets and the sales teams consider the value of the deals lost. The owner of VoC then works with business leadership to combine those rankings and socialize back to the individual teams to get their buy-in. This creates a single top-10 list that the whole business org agrees on.

[via comment] At the end of each episode we revisit the roadmap, and each team plans for the next 6 months. We are definitely open to shifting in the middle of the year in light of new developments. In practice, over the past 3 years we’ve done a good job of predicting where those changes will happen (eg. in new partnership opportunities, deciding which of 2 features we should build first, or the amount of iteration we’ll want to do on a new feature) and we started the year with the appropriate teams accounting for those possibilities in their roadmap.

You are extremely important to us and we value your thoughtful input. Thank you for your feedback! Feel free to create a post in this category if you have any follow up questions about this process. (August, 2017)

Start date and estimated hours
Enough is Enough - BW Integration For Better Dashboards
Future of Asana
How to make Custom Fields visibile on Cards in Boards?
Desktop Notifications
Feature request: show subtasks in lists
Switching from Boards to List View (and vice versa)
iOS file attachments
Custom fields needed on subtasks
Attaching Files from GSuites new Team Drive(s)
Collapse/Summary feature for sections
How we're listening to your product feedback
Real time, two way Calendar integration
Attaching Files from GSuites new Team Drive(s)
Any plans for MS OneDrive Integration? ETA?
Sort Project List
Attaching Files from GSuites new Team Drive(s)
Attaching Files from GSuites new Team Drive(s)
Ability to change comment sort order
Auto justify task copy to left
What's the status of a native Asana Mac app?
Slow, intermittent prolonged delay on Chrome
Feature request: Assign multiple assignees on one task
Feature request: show subtasks in lists
How we're listening to your product feedback
Copying Custom Fields
How we’re listening to your product feedback
Customising the Asana inbox
Attaching Files from GSuites new Team Drive(s)
Column Width in List View
UI change - Project tabs/buttons in tasks pushed down
Attaching Files from GSuites new Team Drive(s)
Paste screenshots / images directly instead of links
Feature request: show subtasks in lists
Make new tasks appear at the bottom by default

What makes a great product feedback post

Hello all! Sara from Asana’s implementation team, with a few tips about writing great product feedback in the community.

We get such rich information from all of you about what’s most important, alongside invaluable insights about use cases and pain points. When we forward this feedback on to product, the most compelling stories contain all the detail needed to understand and prioritize the request. To that end, consider including the following information in your post:

  • Outline your use case. How do you and your team use Asana? Be specific.
  • Frame the feature request in context of how your team is using Asana. The better we can understand how the feature request/bug fits into the workflow, the more streamlined it is for us to help sort and prioritize in our Voice of Customer process.
  • Help us understand the impact this is having on your team. We want to know – is this having a critical workflow impact that’s affecting your team’s ability to use Asana? Is this driving work outside of Asana, or causing roadblocks in adoption? Or, does this feel like more of a nice-to-have?
  • List any workarounds you may have employed. We’re interested in what you may have already tried in lieu of seeing a product change, and to what degree this is solving for the issue.

For example:

  • Our marketing team has moved to a Board view for incoming requests. Each Task in the Project is a request for the Marketing Operations team to fulfill for another cross-functional Team. We also use Custom Fields for Priority and Status, which helps our team prioritize our work.
  • Being able to see Custom Fields on the Board View would save time for our team, as well as help with adoption of Asana.
  • Clicking into each card to see the Priority in order to put the card in the correct column takes a long time, and frustrates some of our reluctant adopters.
  • We tried the same view in a List, where we could see the Custom Fields, but we prefer the Board view for ease of use and clarity of stages.

The above testimonial can easily be categorized with product component and workflow impact, and empowers our customer operations team to specifically prioritize (and advocate for!) this change. In addition, it helps enrich the conversations in the community, as other members can read and learn from your workflows, workarounds and creative requests.

As always, thanks for your partnership and thoughtful feedback :slight_smile: Looking forward to continuing to read and learn from all of you!