Subitems: Single list of Items

GENERAL
In Item View, we want to report on some individual filtered items (regardless of item type) without showing their hierarchy.

SPECIFIC USE CASE
In our current use case, we're looking for completed tasks and projects, assigned to a certain user or user group, grouped by week of completion.

WHAT'S AVAILABLE
The "Subitems" menu has only two options: "Single list of tasks" or "Projects and tasks structure".

WHY IT DOESN'T WORK
We can't use the second option, because everything gets grouped into the hierarchy instead of by week.
But we were disappointed to find out that the "Single list of tasks" option is literal - it does not display any projects.

REQUEST
Please add a third option to the "Subitems" menu to display "Single list of items", which will ignore the item type (task or project or milestone or whatever) and display them all individually, without a structure.

Would prefer not to use Dashboards for this case. If anyone is aware of some way to do this, which I missed, please share.

Thanks!

P.S. If you would like to see this request implemented, please upvote it and ask your friends to. Minimum threshold is 60 votes.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Rohan V

Thank you for posting your suggestion, @Sergey Lyakh. We’ll keep you updated if there are any further developments 👍

Steve Mruskovic

@Sergey Lyakh hi! Have you tried using the new filter options to create a custom view to get what you need? I've just started playing with them and they are pretty powerful, so you may be able to filter out what you don't want to get to what you need. You can also show Folder or Project in one column to see project it is associated with.

Not sure if this is exactly what you need, but it might get you closer.

Sergey Lyakh

Hi @Steve Mruskovic, thanks for the suggestion. We do use the new filter options - I made a whole post about a useful combination of them HERE.

However, we blur the line between tasks and projects in some of our cases and manage some projects without any tasks (like incoming ones generated via request forms). Only the hierarchy view will display all relevant items. But to group them by week of completion or name of requester requires item-only view (no hierarchies), in which only tasks are allowed.

I'm open to other suggestions.

Sergey Lyakh

Hi @Rohan V,
Do you think this is a good idea? Do you know if this would require a significant architectural change, or is this pretty simple to implement? Just wondering if this request has any hope...
Thank you.

Rohan V

Hi @Sergey Lyakh 🙋‍♂️

I’ve noticed that your post has received a few upvotes, so it seems there are other users interested in similar functionality as well. Regarding how difficult this would be to implement, I don’t have an answer at the moment. Typically, once a feedback post reaches 60 upvotes, we check with our Product Team for an update. At that point, a status such as Not Planned, Backburner, Investigating, or Coming Soon will be assigned.

Since this post currently has fewer upvotes, it’s difficult to predict what will happen, but I understand your perspective.

All feedback posts are forwarded to our Product Team, so if there are any developments or updates, we will notify the Community.

Thank you.

Florian Kislich

Hi Sergey Lyakh,

I guess your problem is rooted here:

However, we blur the line between tasks and projects in some of our cases and manage some projects without any tasks (like incoming ones generated via request forms)

Projects are like advanced folders, but they remain folders. I would recommend creating at least one task for each project to handle this (and many other issues) correctly. Especially with request forms you could use blueprints to generate helpful tasks for these projects, it shopuld not increase daily work!

Florian

Sergey Lyakh

@Florian Kislich, indeed, that is the root. But changing that just for functionality's sake brings other complications, like double entry being needed (to update both the task and project) to change status, assign, etc.

We have to report to non-users via dashboards, and that becomes more complicated too, since dashboards can only show one kind of item at a time. So, it's not like we can just focus on tasks only and ignore projects.

These requests are typically minor and numerous, so treating them like true projects just adds unnecessary complexity and clicks/data entry.

Florian Kislich

Hi Sergey Lyakh,

interesting - I would create only a task, if the issue is just a minor one, instead of a project without tasks. Sounds kind of exaggerated to report those items on project level as well. But yeah, maybe that't what you want!

Sergey Lyakh

Hi @Florian Kislich,

I agree that it would be simpler just to create them as standalone tasks, but then we run into the exact same problem: we'll have a mix of projects and standalone tasks, and we - again - won't be able to display both as a list of items (instead of a hierarchical structure).