Kanban Board - Allow Usage for To Dos

What is the challenge?

Our UX team assigns to dos to relevant requirements, such as to dos for "user research" or "create mockup".

To dos are great, because they can be assigned at multiple levels of the planning hierarchy- research can be done at the initiative, epic, or feature level.

What is the impact?

Currently, it is hard for our UX team to manage wok in one place. They rely on a report based on to-dos and manage their work their. But this is really not great usability. We have also done a trial on AHA teamwork but given that only requirements can be used in the Kanban and these can't be attached to different levels of the planning hierarchy, this doesn't really work for us.

And the impact is larger - I am only describing the workflow for UX here but this would be equally great for PMs to better track all the work that is not necessarily feature related. It would just help to evolve AHA a bit more in the collaboration aspect.

Describe your idea

In short: Enable to-dos as a record on Kanban boards.