Smart Filters for Widgets - i.e. (unscheduled) Tasks from Projects planned for current week

We are organizing our ToDos in Sprint-Folders/Projects by calendar weeks. So, there are Projects like "Sprint W07_08", "Sprint W09_10" etc. which are all located in a "Sprints" folder.
The tasks themselves do not have a due date but are set to backlog.

It would be great if there would be a possibility to create a Widget "Current sprint" which would filter like "All tasks from Projects which are planned for this week inside "Sprints" folder".

What's missing is a filter "is in" wich can be dynamic - not just a fixed folder/project. Like "Is in a Folder/Project with these properties: [Project/Folder properties]"

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Florian Kislich

Hi Lutz Otto,

I support your idea, but there's already a way to achive your goal (with one aditional step): You could use a custom (checkbox) field, let's name it "Sprint", and use it to filter your dashboard. In combination with due date, you won't even have to uncheck it afterwards.

Florian

Lutz Otto

@Florian Kislich
Thanks for your suggestion. In that case we'd need the tasks themselfes to have a duedate. (Filter would be "IS 'sprint' AND 'due this week'").
I also tried your approach in combination with automations but there is no trigger like "Due-Date of containing element changes" (start date nad end date could do aswell) to set the due date of the containing items. I can't access data from elements in a higher hirachy. It's only possible to use predecessors but that does not help in our case.
When using automations it would be great if there would be:

For Tasks:
A trigger "[FIELD] of parent element changes"
Access to Data of parental elements

For Projects/Folders
Actions like "Change [FIELD] of children to [VALUE] ->

Florian Kislich

Well, I guess tasks in general should have a due date, that's how Wrike works. What about setting the due dates of subtasks using the drag function of the table view? I would prefer this prior to automation, because you'd always see if there are special tasks which need a different due date.

Rohan V

Hi @Lutz Otto 👋 thanks for posting. As @Florian Kislich mentioned, for now, the most practical approach might be using custom fields to identify current sprint folders/projects. I've shared your post with the relevant Product Team for their visibility. If there are any developments regarding your suggestion, I'll be sure to post an update here.

Thank you, Florian, for stepping in and helping our community members, as always!