Skip to main content

Richer task descriptions with markdown tables and clean paste

Features & Improvements RequestTasks

Better task description

Task descriptions are limited, so complicated work ends up on a linked Notion page instead of in the task itself; coming from Trello the expectation is to keep all the information in one place. Task descriptions should at least support what is provided by markdown, including simple tables, and pasting text out of Teams, Notion, Outlook and similar tools into the description should produce an acceptable result.

Posted by Sven ·
Status: In Review2 comments

Log in to comment and vote

Comments2

  • Linked to Comment Box on Tasks: Ability to add a comment section inside each task to record changes, updates, and notes.

  • Tadej J.

    Team•

    Oct 10

    Hi Sven, thanks for explaining this. Akiflow supports basic formatting in task descriptions, but not tables or full Markdown support today.

    Could you share one example of content before copying it and how it looks after pasting into Akiflow? Please remove any private information. That will help us identify what breaks and whether we can improve the existing editor separately from adding tables.

    • Sven

      •

      Oct 13

      Hi Tadej, nothing to show here. It was a simple Teams message with a table with two colums at the end showing a list of initiatives (column 1) and when they will probably be delivered (column 2).

      Probably I could even live without the tables. The main issue is, that the description in Akiflow is too small and requires too much clicking, so that I don’t want to write there more than a few lines of text. But in many cases I have more than that to write down – my goal always is, to keep all relevant information in one place, so that I do not need to open other artifacts.

      For a keaboard based tool, markdown is, what makes me fast. In your editor headings don’t even have a shortcut. In markdown I quickly type # and Space and I’m done.

      So I mostly end up creating a notion page and linking it on the task, but that requires additional navigation and cleanup work.

      This together with the missing comment feature is the only reason, why I’m evaluating Sunsama at the moment, though I like Akiflows UI and scheduling buckets (next month, etc.) so much more.

      Even if working alone Akiflow, comments are crucial to log further information (“Asked x via mail …”, “Waiting for y to provide template …”)