Here's what a single task looks like in TaskJect
When designing TaskJect, one of our main goals was simple:
Make the task view as informative as possible — without any noise.
Everything you need fits into one clean screen:
Task title and description
Assigned user, deadline, complexity
Priority and status
Notes from the Team Lead
Time tracking & progress
Created date and task owner
💡 This helps teams:
Understand the task instantly — no extra clicks
Keep clarity even a week later
Work more efficiently — when each task carries context, not just text
(The screenshot shows a real task from our dev roadmap: adding file attachments)
We’re improving TaskJect every day — and curious to hear from you:
👉 What’s a must-have in your task view?
Got an idea to make it even more convenient? Drop it in the comments!
Love how everything critical sits in a single panel. really good. I don't know if I missed it but is there a possibility to add subtasks ? It's a must-have for me so I don't know if you thought about it.
Thanks a lot! Glad you like the focused layout 🔥
At the moment, we don’t support subtasks. But if our users identify it as a must-have — it’s definitely something we’ll prioritize and implement. We always listen closely to real needs rather than building just in case.
Love the clarity of your onboarding flow — especially the table view!
Instead of going the traditional board/column route, we’ve been experimenting with a tag-first approach to avoid the clutter that boards can create over time.
Curious — did you explore any alternatives to columns during your design process, or was the board view always the direction?
Thanks for the thoughtful question!
We actually follow a linear task flow, so our board uses a fixed set of columns to reflect that structure. That said, clutter is something we’re careful about — by default, we apply a filter to show only tasks from the past month, so older tasks don’t get in your way.
We’ve also recently introduced a table view, which focuses by default on tasks that are either not started or in progress, again to avoid visual overload.
On top of that, we’re heavily user-focused. In our Pro and Expert plans, users can suggest features or improvements directly — we aim to solve real problems that our users face, instead of adding features just for the sake of it.
Always happy to hear new approaches, though — your tag-first idea sounds really interesting!
For me, quick access to related tasks or dependencies is a must. It helps a lot when you're working on something that’s part of a bigger flow.
Absolutely! That’s exactly why we show your active tasks (up to 10) right in your profile — with quick access to their projects. Makes it much easier to stay in the flow
> "Interesting product! Good luck with your launch."
Thanks! If you're curious to try it out, feel free to give it a spin — would love to hear your thoughts!