A project's subtasks should be created when project is approved (not submitted)

The reason why we should not want the subtasks created until after the project's approval is so the subtasks' assignees are not presented with tasks that may not be approved and they should not be interrupted with potentially invalid work requests.

0
7 comments
Spot On Innovative Approach Stellar Advice
Avatar

Thanks for posting, Tod Bassler! It would be great to know a little more detail on how you manage projects. For example, are you using Blueprints in your account? When you add an assignee to a task blueprint or an owner to a project blueprint, it isn’t automatically shared and an assignee/owner doesn’t receive any notifications. So you could create a project with tasks, assign team members to those tasks (they won't receive notifications yet), and then get it approved. After that, you can launch the project from this blueprint. Please let me know what you think 🙂

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Lisa,

Yes, I am using Blueprints for tasks but not projects.  Here is what I have:

(1) A project is built from a Request form and it will have tasks dependent on the requester's anwers in the Request form.

(2) Once the project of approved, each person should then receive their task(s) (but not before approval).

Does this make sense?  Thanks, Tod.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for getting back to me, Tod Bassler

Would it help if the team members will receive their tasks, but the status of these tasks would be "Not approved yet" so that it's clear that it's not time to work on the task yet? 

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Lisa,

Are you referring to creating a workflow with an [Active] status of "Not approved yet"?  If so, would all of the project's tasks then be able to switch to status of "Approved" once the project is approved?

Thanks, Tod.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Tod Bassler, yes, that should soon become possible with Wrike's Automation. Once the "change children status" action is released, it will be possible to automatically change the tasks' statuses to "Approved" once the project's status is "Approved", and it's also possible to add an @mention and a comment - it can be something like "This project is now approved, you can start working on this task", for example.

Please let me know if that would be helpful in your case 🙂

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Lisa,

Yes, this feature of Wrike's Automation Engine will be quite useful for us!  We have a Business subscription.

Do you know the ETA for this feature's availability?

Thanks, Tod.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for getting back to me, Tod Bassler! I don't have the ETA yet, but I'll announce this on the Community as soon as it's released. It says "Coming soon" in Wrike when you look at the list of available triggers and actions, so it shouldn't take too long 🙂

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink

Folllowing List for Post: A project's subtasks should be created when project is approved (not submitted)
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post