Creating a subtask from a comment lets you capture work right where the discussion happens. You can also anchor the subtask to an exact spot in the file so assignees land on the right context. In Burai, comments, tasks, and file context live together, so assignees can open the task and see the anchor inside the File tab.
Steps
Write your comment and @‑tag at least one user.
Type your comment and include @Name anywhere in the text.Turn the comment into a subtask.
When Burai recognizes an @‑tag, a checkbox appears above the input. Check Create subtask and assign to tagged user(s).
(Optional) Choose who gets assigned (when multiple tags).
If there are 2+ tagged users, click the arrow next to the checkbox to open the list.Click All to assign everyone.
Or pick specific names. Avatars of chosen assignees appear.
(Optional) Add an anchor to the exact place in the file.
After you check the box, two icons show in the top‑right: Select Spot and Highlight Text.
Hover to see a tooltip, then click the button you want to proceed with.
If you want to change the location or reference you selected, click Change to clear the current selection and pick a different location.
Post the comment.
Burai creates a subtask with:Title prefilled with the full comment text (including tags).
Description prefilled with the full comment text (including tags).
Assigned to prefilled with the tagged user(s).
The assignee(s) receive a notification.
Open the new subtask to verify the anchor and activity.
In expanded task view, within Activity, you’ll see “Jane Doe created this task from a comment.”
Clicking the linked phrase ‘a comment’ opens the task that contains the original comment.
Notes / Tips
If you don’t check the box, Burai posts a regular comment only.
Subtask anchors open inside the File tab so assignees arrive on the exact spot of the document.
You can anchor either by selecting a precise text highlight or by choosing a spot (great for non‑editable files).
Summary / Next Steps
Use the checkbox above the comment box to create a subtask for your @‑mentions, and add an anchor for precision. This keeps work actionable and in context.