This is something that definetely will keep my company on asana. I really love asana, but I would love it more if we have a knowledge base section where we can freely write and customize as notion does. Markdown, code snippets, images, etc. Right now we are using notion but it would be much better to have it all in asana.
2 Likes
I agree. I have been hoping for what someone provided a mockup of above, an ability to mark a Task as āarticleā or ādocumentā, similar to the way you can mark a Task as āmilestoneā. When marked the Task would no longer be ācompletableā and no longer count in a projects completion status.
Clickup was the first example I thought of as well where this type of thing was implemented in this way.
Asana is really already about 95% there for having a built-in Wikiā¦
- Task description that supports long format text? Check.
- Task (article) description that supports Markdown? Partial check. Asana support their implementation of Markdown, which is greatly improved with the recent addition of Headings (H1, H2). While not as full an implementation of Markdown as Clickup or Notion, it is quite adequate, at least for our use.
- Quick/easy cross-linking of Task articles to other Task articles and Projects? Check.
- Ability to display images inline in Task (article) description? Check, thanks to the recent update.
- Ability to lock Task (article) to read-only? Check, though I do understand that some would like to also prevent comments.
Really, the only thing Asana is missing from my perspective is an ability to identify/mark specific Tasks as article/document and remove the complete/incomplete parameter for those Tasks.
3 Likes
Good suggestion. That is almost exactly how weāve āhackedā Asana to also be a wiki for us. For most projects we have an āInfoā section and then for every Task that is just and āarticle/document, not to be completedā Task, we prefix the Task title with ā(INFO)ā. Itās a bit of a pain, but Iām so used to it now that I donāt think much about it.
For Projects that have the layout saved to only see the Incomplete Tasks, we ask everyone to NOT complete the (INFO) Tasks. For Projects where the layout is saved to show All Tasks, it doesnāt matter, other than for the Project stats, which means that many times the (INFO) Tasks are marked completed to more accurately represent Project status.
This āworksā for us, but we certainly would love to see Asana add just one small feature to make this idealā¦ allow a Task to be marked āarticle/documentā, like it can be marked āmilestoneā and then remove the incomplete/complete option for those Tasks. DONE. That is all that we would need (want).
BTW, we also use this same technique for the meeting Tasks we create. We prefix all Tasks that are used for meeting notes with ā(MTG)ā and keep them in a āMeetingā section that was also include in most projects. These have also worked great for us, because meetings many times end with Action Items and we can just create some SubTasks and link them to specific projects and know which meeting and decisions led to their creation. It actually works really well already. (we would still like to be able to mark this Tasks as āarticle/documentā though ;-)).
2 Likes
Sounds like you have smashed it! It certainly would be great to see some tasks that cannot or do not need to be completed too 
and some nice suggestions too about the prefix.
I have seen so many improvements made to Asana over 2022, so Im sure the team will continue through 2023
1 Like
Has Asana made any progress on this? Or is it just Asana2go and Slab? Is Slab a good alternative? I havenāt seen anyone mention it in detail.
Hi, I just wanted to bump this because there seems to be a bit of confusion from the staff about what it is people are actually requesting. I mean what Iām about to say with the utmost respect as Asana is already a 98% tool, but when people are asking for a wiki, they are asking for exactly that. Not a clunky workaround using read-only tasks or anything like that, and even the project brief section at least to me is lacking.
Wikipedia. We want that. We want a database of documents where we can hyperlink words to other documents. Obsidian does this really well, the only issue with Obsidian is there doesnāt seem to be an option where the company can pay per seat and individual users have to pay per seat to view a shared Wiki.
I really hope the staff does read over this comment because this is like, the one thing that Asana just doesnāt do and Iād really like to centralize my project management within Asana but there is just no way I can create a wiki or KB with clunky workarounds so at least for the moment, Iām just going to have to use another software for our Wiki.
3 Likes
I am really split about this: the wider the feature footprint becomes, the more the dev team and product are spread thin and the less time they have to improve other parts of the tool.
Many people use Asana+Notion for wiki. Or Asana+Hubspot for CRMā¦
Hi, I am new to Asana.
I notice there was a discussion about Asana lacking a wiki functionality back in 2019 but I donāt see much since. Does anyone know if this is something they are considering in the future? Is there something in Asana right now that I am missing that can be used for that function? How are you managing this missing feature - is there an integration that I can use?
Thanks.
1 Like
Welcome, @Karin_Davis,
Iāve merged your post into an existing thread where you can click the title to scroll to the top and vote by clicking the purple Vote button.
You can check the posts here which may provide some answers.
Asana doesnāt reveal its roadmap but will update this thread if/when something changes.
Many of us use the existing features of Asana projects, but just make sure to make the permissions default to āCommenterā to tasks are not able to be marked complete. Thereās linking, vanity links, levels of hierarchy, etc.
There are integrations which may or may not be helpful (for example Confluence) at Asana Apps and Integrations ā¢ Asana.
Thanks,
Larry
Just adding more support for this to become a feature! Weāre currently using Sharepoint (not well, tbh) to manage an internal wiki/knowledge base, but itās too confusing for most of our team to navigate, super convoluted to make changes/updates, and it makes more sense to keep the workflows/supporting docs in the same place weāre asking the team to DO the daily work anyway, rather than linking out to stuff stored somewhere else. We want to move EVERYTHING into Asana (within reason, obviously), and creating a useful Wiki would help us do that, and make life insanely more simple for our team.
1 Like
I appreciate your response, but Iām looking for direct corrections and improvements only. Thank you.
Just adding that one of your biggest competitors has this since long ago:
https://clickup.com/features/docs
This is exactly the feature that we would need
5 Likes
We are using You in conjunction with Asana and so far - itās great! I wish it could be in one project as well
1 Like
we urgently need this feature. This feature is currently my No 1 reason of considering switching our organisation to ClickUp. Instructions for processes especially in our marketing department need to live somewhere, should be inside Asana instead of google Docs. Most companies in e-commerce use Notion or Clickup or a messy collection of google Docs. Having it all in Asana would be very beneficial.
@Johannes_Pautzke did you consider the new Notes tab in projects?
Notes tab is not necessary. People can keep their notes in tasks. We need a wiki or knowledge base style documentation section.
Hi Sinan!
The ānotesā tab can be renamed whatever you want and lets you embed images and videos and can be set up like a wiki very easily.
1 Like
Can you describe what exactly is missing from Asana at the moment? With Notes view, and the ability to have several notes, it feels pretty close.
I believe an automated index is missing.