Being able to have a trigger for a rule based on start date would make my work so much better. At the moment I have to set due dates for whenever I’m going to start work on something so it will actually pop into my “Today” section on the day I want to be working on it.
Added my vote. This is a pretty significant gap and requires a lot of manual overhead to manage – in other words, it actually introduces the dread “Work About Work” that Asana is meant to reduce.
It would be really useful to make Rules based on a task start date, just like the Rules based on a task due date.
I use a kanban-style board to track ongoing projects, and each project has its own task. Two columns I use frequently in my board are “Planned & Upcoming” and “In Progress”. Once the start and due dates for a project are established, it would be helpful if the corresponding task automatically moves from “Planned & Upcoming” to “In Progress” once the start date arrives.
@Danny_Harrington, I think this duplicates my request from a while ago so I’ve moved your post there where you vote will count toward that request.
Thanks,
Larry
Has this not been solved yet… would be really useful to be able to build rules on start dates!
@lpb , thank you for moving my post! Sorry that I didn’t see yours first.
Cheers,
Danny
As someone trying to track sprint velocity, it’s useful to create dashboard/reports to compute the average time to complete a task of a given complexity. I would love to have a rule that sets the StartDate to today whenever a task is moved to our Development swimlane. Then, I could modify my reports to calculate the average time from Start Date to Completion grouped by Complexity.
Is there any update on this suggestions from May? This is a critically needed feature. My fingers are crossed this is underway.
Any updates on this? I desperately need a subtask to be created triggered by a Start Date but there is no option for this.
I have Flowsana, which I pay for, but the options of Flowsana have disappeared from the Create Rule section so I have to resort using the Flowsana website and it’s not easy to use. Plus is can’t create subtasks without a template task in another project to copy from.
Very frustrating this doesn’t exist.
Those options are still there! Can you send an email to support@flowsana.net so we can discuss further why you are not seeing them?
@lpb , thanks for pointing out this thread. I have added my vote.
I am not sure how much confidence I am placing in the feature voting as this thread is coming up on two years old.
TBH, it seems to me the community managers are kind of repetitive in their replies, e.g., “Thanks for your feedback. This is similar to another thread so I am merging yours into that one.”
I’m new-ish so I don’t want to be overly-critical of anything. And yet, it feels like the forum is less about discussion and more about pruning and housekeeping of posts, i.e., how quickly can we call this “resolved” or “answered” or “no longer accepting comments”,
Has most of the important discussion already happened in the past? Is Asana resting on its laurels?
I am getting concerned that maybe I should not be investing my energy in Asana. Has it played itself out?
@anon23352771, I respectfully disagree with virtually every point in your post, but appreciate that you feel differently.
Two hours ago @Marie posted this month’s release notes; many updates this month alone address popular and key Forum requests:
Looking back at previous updates, you’ll note many more such updates and an increasing velocity.
Here’s the process Asana uses to evaluate feedback and prioritize, incorporating more than just the Forum:
Community Managers and us Forum Leaders (volunteers) always try to do our best to make the Forum a useful resource to the 200k+ users here.
Thanks,
Larry
@lpb - yes, I was clearly, “That guy.” I overstated and oversimplified and generalized at the expense of good manners. I apologize. There’s really no excuse for that kind of rudeness, especially from the “new guy” to people who have been serving this community for so long. I am sorry.
For my part, there was likely some frustration on the thing I was trying to research and finding it to have such a very long history. And, too, I have been told that I come off harder and sharper in writing than I do in person. It’s a thing I am trying to work on.
Thanks for taking the time to so graciously giving me a better perspective.
Thank you for that thoughtful reply.
We’ve all been “that guy” on occasion (present company included!) but not always willing to write such a nice follow-up as you did. Thanks for taking the time to do that, and all is forgiven!!
Larry
Another vote for this oh so useful request - I think of it like this, procrastinators work to due dates, vs precrastinators who work from start dates! I need to be able to do workflows and filters from start dates - please make it happen!
Thanks, @anon23352771 - just have to say this exchange with @lpb is a perfect representation of why I love this community so much! (And yes, we’ve all definitely been “that guy” on occasion!)
I just led an Asana Onboarding Session with new team members (How to use “My task”). I also showed them how they can use rules. We did some hands on work and one of the first questions that was asked was: “How can I trigger a rule by start date of a task”?
I could only tell them that it’s not possible and that I don’t know why this is not getting implemented. And that it’s personally my singe biggest pain point with Asana,
Any news on that?
As of this post, the thread is two days shy of its second anniversary. Is there a precedent for a feature request sitting for this long and still getting implemented in Asana? If so, is there anything further we users can do to raise the profile of this request or make it more likely for Asana to invest some development resources into it? I’d put all ten of my votes into this if I could.
Sure, there are requests that were here for a lot longer than that which were implemented. It’s important to remember that forum votes are important but are only one of multiple factors that Asana uses to decide what to implement.
I would say, for those customers who have a dedicated account rep, let that rep know how important the feature is to your Asana usage.
Welcome, @Andrew47,
In addition to what @Phil_Seeman wrote, see also the following for more info:
Thanks,
Larry