Hey Graham! 
Guru doesn't have a built in way through the Editor to create a checklist, but you can create one using Markdown! I've linked a helpful resource that breaks down how to do this here. It's important to note that the checkboxes won't remain checked after closing/refreshing the Card. If you need the checks to persist, I recommend creating a table for the list with a column dedicated to the checkmark and to use an emoji in that column.
This is perfect, thank you!
@June Zhang Can you elaborate on what you mean by use an emoji for the check box? How does that work exactly?
@ShayeRyan You can insert a
emoji into a Guru Card to signify that the item is checked off or completed. On a Mac, you can use ctrl+cmd+spacebar as a shortcut to open the emoji keyboard. On Windows, the shortcut is Windows + ;.
How are you hoping to create a checklist in Cards? Let me know how that idea works for you, happy to discuss any other thoughts you might have.
@June Zhang Thanks for the idea but I’m looking for something a little more interactive such as an actual check box that you can click and check. Similar to the the markup version but the check box needs to remain when closing the tab. I’m trying to setup a checklist for onboarding clients.
@ShayeRyan Unfortunately, our current Editor and markdown capabilities don’t support creating interactive checklists like you’ve asked for. Several other customers have expressed the same interest in a checkbox feature in Guru, as you can see from the discussion and upvotes. I encourage you and your team to upvote this feature, as our product team directly leans on this feedback for future roadmap considerations. You can also subscribe to this post to follow along with any other customer ideas and updates.
In the meantime, the best workaround is the manual emoji checkbox like I’ve suggested. Appreciate you working through this for now!
I will do that, thank you!
Just putting my hat in the ring for this feature. Honestly it seems like a must have and would make Guru even more appealing. I appreciate the suggestion to use a table, but it’s not as user friendly as an actual checkbox. I am also creating one for onboarding new hires.
Thanks!
This would be ideal! We want to use Guru for our onboarding process and would love to have employees check things off within Guru. Definitely something good to consider adding!
I see this thread was posted a year ago, I am here like everyone else also desiring a checklist feature in Guru for new hires. Guru without a checklist feature is like a peanut butter sandwich… Where’s the jelly? Dry cereal is cool but milk makes it better. Do you eat your pancakes without syrup (if yes, stay quiet. Trying to prove a point)? I love Guru, its great. But can we please get a checklist feature?
Hi everyone,
Laura from the Guru PM team here. We appreciate your continued feedback on this topic and understand that the Markdown option doesn’t fulfill what you’re looking for. We don’t have anything prioritized in this area at this time but I’ll leave a few questions here that’ll help us understand more about how you’d like to this to work if we were to prioritize it:
- Would you expect the status of each item (whether it were checked or not) in the list to persist across sessions in Guru? For example, if someone left off in the middle of a list and came back a month later, would you expect it to have maintained what had/hadn’t been checked off?
- What would you want to happen to the status of checklist items when editing a card?
- Who would be allowed to check off items in the list? Same set of people who can view the card? Would you want it to be a special permission? If multiple people can view a card, which of them can interact with the list? All? Some?
- Related to #3, when publishing a card with a checklist in it would you make that card visible to a very limited set of people or many? Why?
- Besides onboarding, what types of cards would you use checklists in?
Thank you!!
Hi everyone,
Laura from the Guru PM team here. We appreciate your continued feedback on this topic and understand that the Markdown option doesn’t fulfill what you’re looking for. We don’t have anything prioritized in this area at this time but I’ll leave a few questions here that’ll help us understand more about how you’d like to this to work if we were to prioritize it:
- Would you expect the status of each item (whether it were checked or not) in the list to persist across sessions in Guru? For example, if someone left off in the middle of a list and came back a month later, would you expect it to have maintained what had/hadn’t been checked off?
- What would you want to happen to the status of checklist items when editing a card?
- Who would be allowed to check off items in the list? Same set of people who can view the card? Would you want it to be a special permission? If multiple people can view a card, which of them can interact with the list? All? Some?
- Related to #3, when publishing a card with a checklist in it would you make that card visible to a very limited set of people or many? Why?
- Besides onboarding, what types of cards would you use checklists in?
Thank you!!
- Yes, if we created a card with a checklist, we would expect each item to still be checked off (marked complete) whenever the card was referenced in the future.
- The items should remain checked unless they were cleared when editing a card (wish list would be to have the option to clear or “check all” while editing).
- For our current purposes, anyone who has access to the card would be able to check off items on the list, though not the permissions to edit the card. The check boxes would be the only items editable on the card; you wouldn’t be in edit mode while checking off line items in the card.
- Cards would be available for certain teams. For example, only managers/HR would have access to an internal employee onboarding checklist and an accounting team would have access to a client onboarding task list. As it stands now, we have a card listing each step that needs to be completed to onboard a client, but we have no way to see if/when each step has been completed by someone else. We could build this out in another system, but it becomes cumbersome to be referencing & managing tasks in multiple systems for each client and employee. Also, each employee doesn’t have access to all systems; marketing wouldn’t have access to a set of tasks in an accounting system, for example, and accounting doesn’t need regular access to a project management system used by admin & marketing.
- We would primarily use the checklist cards as templates and create a new one for each client, which would then be saved in the client’s Guru board for future reference for which steps had been completed during onboarding, which systems were selected by the client (such as which payroll platform, receipt capture app, payment cards, etc.), and if anything was left incomplete. Same for an employee onboarding - new checklist card for each employee, which would then be saved in our HR collection for future reference for HR/managers.
Thanks!
Just adding …. we just rolled out Guru and its been a success so far. When I pitched the idea of using it for onboarding new hires in specific depts. the general consensus was “how do we use this to check off milestones, or that someone has done XYZ task?” … people were not getting it and preferred using a Trello or Asana board.
- Would you expect the status of each item (whether it were checked or not) in the list to persist across sessions in Guru? For example, if someone left off in the middle of a list and came back a month later, would you expect it to have maintained what had/hadn’t been checked off?
Yes, I would expect the status to persist, as though it was an update to the card. - What would you want to happen to the status of checklist items when editing a card?
I would hope to see the checked items remain checked, and unchecked remain unchecked. The “living” element of the card would remain “living”. I could see the need to add additional tasks after someone started to check off boxes. - Who would be allowed to check off items in the list? Same set of people who can view the card? Would you want it to be a special permission? If multiple people can view a card, which of them can interact with the list? All? Some?
I think whoever has read permissions should be able to check off items. A second iteration could be to add permissions for a single user to view the card. - Related to #3, when publishing a card with a checklist in it would you make that card visible to a very limited set of people or many? Why?
I think the same types of permissions that currently exist would work for most use cases. - Besides onboarding, what types of cards would you use checklists in?
In addition to onboarding new employees, it could be used for onboarding new customers or creating a high-level project to-do list.