Sort tasks issued from request forms by creation date
The tasks can only be sorted by due date. It would be nice to have the possibility to sort by creation date (useful for working in a ticketing mode). Also, would be good to have it in the table view.
Hi Marie-Pierre, thanks for adding this suggestion here! This sounds interesting for both the List and Table View. Something I wanted to suggest in case it helps, since you mentioned that this is for working on tickets, is setting the due date to correspond with the creation date. This will allow you to sort by date both in List View and in the Table, and easily keep track of all incoming tickets. Do you think this could help for your use case?
I agree with Marie-Pierre. I would like to be able to sort my tasks (in my work or dashboard view) by the date they were submitted. If I have 15 tasks due today, I'd like to sort them by when they were created so that the first request gets completed first. Alphanumeric sorting is putting some projects and tasks at a disadvantage and date alone isn't granular enough.
Any status on this? It is really annoying that when you have a big load of tasks you can't figure out which came first.
Hi, I agree this would really help.
We also would need this feature - at least for the list view.
We also would need this feature - at least for the list view.
Hi guys, thanks for this. Our Product Team are always looking to enhance Request form so I'll be sure to bring this feature request to their attention! 👌
We have a request form where staff can request help from our Facilities team. Facilities requests are prioritized based on resources/feasibility, so the Facilities team triages the requests primarily by request date. They need the ability to sort by request date in order to triage effectively.
We can't use the workaround suggested by Anastasia, as this approach co-opts the due date field, meaning that they would no longer be able to use the Due Date for tasks that truly do have a deadline. In addition, this approach would cause all tasks to show as Overdue, which isn't correct and can cause confusion and morale issues.
We would also like to track when an item was created and how long it takes to complete it. Start and End dates provide reporting on duration and length of time to complete a task from when it was initiated. We would like to see how quickly we are able to resolve items from the time they were identified and measure how quickly we can take them from idea to inception. Wrike, this was identified in March 2017 (maybe even earlier), but you have not acted on it. This "time to action" vs "actual duration of task" tell different stories.
Hi all, thanks for your continued support of this post!
Right now, changing the ability to track the creation date/time is not something on the short-term roadmap. This is due to many other essential enhancements which need to be complete before something like this can be researched. The Wrike Workspace is a real-time collaboration tool, so developments can often be deferred or delayed because of how they affect other actions in the Workspace undergoing development.
For now, it would be interesting for our team to know if this is primarily for use from Request forms, or something you'd like to track through all items that are created in Wrike?
Also, please keep voting and providing a real-life use case. Both of which show the product team how this enhancement can really help your team. Thank you
Our use case would actually be based on when the task changes to a certain status. We kick off templated projects which have a variety of tasks. We generally try to assign them all at that time, but occasionally the project is not completely ready, so tasks go on hold. Of these tasks, hundreds are assigned to our design team - they need to know which to work on first. The date important in this case is when the task is assigned to them (either 'assigned' status or the designer changed to the assignee. This way, as they're looking in their dashboard at their dozens of tasks due in a day, they can work on those which were assigned to them first. Today they have to guess based on naming convention - but they generally just work in alphabetical order which is unfair to customers who have higher account numbers. Happy to help elaborate if you have other questions.
For our team this mostly applies to tasks created by request forms. As Laura Boylan mentions above, we don't want to simply set the Due Date to the creation date because we still need that field to set when the task is actually due. But for prioritization purposes, we also need to see when each task was submitted/created.
For our workflow, the creation date/time is part of the context within which the real-time collaboration exists. If the creation date is ignored, it becomes easier for certain tasks to be perpetually low priority.
We use Wrike for non-software tasks and projects related to property management and healthcare. Therefore the way some of our tasks are prioritised changes depending on how much time has past since creation. If I'm running a team of people who have some autonomy over their tasks, I don't want them to have full flexibility to defer or delay based solely upon how the task affects other action. Some stuff just has to be completed within a set time from the creation date. And when our ability to do that is out of alignment with the resources committed, we know we are either over or under resourced, or that the team is performing differently than expected. To be honest it is hard for me to imagine a scenario where I wouldn't check a batch of items against their creation dates.
Also we'd like this feature for all items, not only request forms instances.
I suppose this is still under the standard corporate response of "thank you but we're not building this now" category? Seems like a very obvious thing to add given the volume I'm sure some teams deal with.
In our case a public form processes about 50 cases per day and other tasks created about 25 per person per day. So teams are kind of lost to prioritize them in order of creation which is what generally makes sense given the First in First Out principle for most processes.
Any news on this? we're pretty much at a stand still and migrating to AirTable for one of our workflows (50+ tasks per day among 7 people) because they can't order their tasks by FIFO (first in first out)....incredibly shocked that this is not a feature that has not been thought through or acted on since it's not really a feature request; it's very very basic.
Hi everyone, quick update: it is now possible to sort by Date Created in the List View 🎉
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Thanks for taking our suggestions! this is super helpful and changes a lot of inefficiencies. 🙌💪