Thank you for your feedback!
Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!More about Product Feedback
Folllowing List for Post: ⌨ Releases-History, Hitting Send, and Houdini (12/19/18)
[this list is visible for admins and agents only]
Send a Comment with "Enter" Best Update EVER!!!
Thank you for finally adding custom field history!!!!!
And re-sending Invitations in mass!
(Also happy new year everyone)
I just thought,
Is there any plan for changes to custom fields to be included in the comments stream of a task too (togglable)?
Thanks for getting back to me in advance
I am excited to try blue prints… I am often trying planning projects and driving users crazy with all the emails!
@Jennifer, curious, what are blue prints?
@1Marjorie looks like I commented on the wrong release note but here is a link to blue prints
@Marj, glad to hear you're happy about the enter button change, I was delighted we finally got this added to Product roadmap. It came from a really strong push from Community, so thank you to everyone here!
@George, thanks for the feedback around adding this detail to the Stream. Currently that's not in scope but it would be great if you could start a Feedback post so we can start collecting votes and use-cases (if you do add a new feedback post please add your own use case please, i.e. how this would help you and how you'd use it so our team understand the value 👍)
@Jennifer, Blueprints is super exciting, please be sure to let us know what you think, and any feedback you have is super important to the product team while it's in Labs 👍 And @Marj, I think you'll really like this new feature, give it a go 😊
Hope you all enjoyed the holidays! Happy 2019 🎉
I've made a feature request regarding notifications from custom fields appearing in the task's stream / your emails (if anyone thinks they might also find this useful).
@Wrike The links at the bottom to Marketing and On-boarding communities are reversed.
I am so glad to see these changes. I am also excited about Blueprints. I think it will be something our users will really love. I am hoping a video tutorial will be put together and shared as well. I think that will really drive home the benefits to users. Great way to start the year off Wrike!!! :)
@Sara Opps, I got things a little flip-flopped there 🙈 . Fixed it, thank you so much for letting us know.
@Melissa Glad to hear you're excited! I'm personally about to dive more into Blueprints today and move some existing templates to a Blueprint 💃. The team sometimes waits until things are out of Labs before creating a tutorial video but I'll make sure to let them know that this is something you guys really want.
@Stephanie - so do you think moving the existing templates will be beneficial? I was thinking of doing that as well but didn't know if it would provide any benefits other than them all being in one place. I did submit it as feedback but that would be great if you could also let them know.
@Stephanie, if i'm reading this correctly in regard to Blueprints, they will, in essence, be our templates? So the current templates i have, i should move to blueprints? I love this! My assistant will appreciate not getting the 1,000,000,000 notifications from me setting up a template/blueprint. 😂
@Melissa @Marj I feel like we're all going through very similar things right now, I'm taking a break from setting up a Blueprint to talk about Blueprints here 😂. One of the main benefits is that Blueprints allow you to have items set up (Folders, Projects, etc) with assignees/dates and those assignees won't see the tasks in their My Work, Dashboards, etc. You can then choose to have assignees notified when the Blueprint is launched.
I also really like that there's a small bar at the top of Blueprints that let you know that it is a Blueprint which will hopefully help people know not to use the Blueprint as their actual project. I'll keep sharing as I build out things - I would love to hear what you guys discover though!
I hadn't even noticed the small bar, I like it. Question, i have blueprints that are not shared. My assistant uses a Request form (remember to update the request form to use the template) to create a project automatically. Can she then see the project if items are assigned to her? Can she see ONLY the ones assigned to her, or the whole project? If i can hide all my blueprints and have them auto create projects and tasks that can then be seen, that would be the BOMB! 💣💣💣💣
@Marj, that's exactly it, it really is the bomb 😃💣
Like Stephanie, I've been testing this out and making Blueprints from my existing Templates and also created one or two - I love it!
You can create the Blueprints and choose to hide them. Once a Request Form generates Folders/Projects/Tasks from Blueprint it can then be seen by anyone who has that Request Form location shared with them - as usual.
Here's some other information I've found.
Request Forms work the same regardless if you create the Project from a Blueprint or existing Template. Little more information added here about this.
Your assistant won't see your Blueprints, even if assigned to its Tasks unless you choose to share the Blueprint. Sharing and access to items within the Blueprint happens when you @mention or add someone as a Follower.
If you choose to launch a Project/Folder/Task from a Blueprint you can specify whether you want the assignees of Tasks to be notified in their inbox when it's created. Regardless if you choose to notify assignees, they'll still have access to the newly launched items.
I hope that helps 🙌
I just used a request form, unaffected by the new blueprints, as it only creates a task and places that task into a folder. It also auto assigns to a specific person, which is configured on the Request form. I tried this with 2 different request forms like this, and i did not get a notification that i had been assigned a new task. I'm pretty sure i used to. It's very important i know i have new tasks coming in.
UPDATE: If i do a request form, that ultimately will assign the task to me, no notification. If someone else does a request form that auto assigns to me, i get notified.
What I would love to see and I'm not sure where the ask really belongs, here or with request forms. I have a request form that is pulling from a blueprint that has sub-tasks. The sub-tasks are high level and generic like "Graphic Design" and "Writing Content". The form title will become the main task name but the sub-tasks remain generic. Here is an example - The name of the main task is "FB post for New Year", and sub-task remain high level "Graphic Design" and "Writing Content". We get several request a day so to the person that is assigned to "Graphic Design" and "Writing Content" now have 10+ tasks all named the same thing. I would like to be able to add the task name "FB post for New Year" behind the sub-task title, "Graphic Design - FB post for New Year" and "Writing Content - FB post for New year".
This addition would allow the assignee to see each task as a individual ask without having to dig deeper into the main task.
In a perfect world, the prefix could go at the end of the task/project/folder, however, Wrike only offers Prefix ability. I created a test project Request form. If you select the Add prefix for all tasks and subfolders, the answer to whatever question you choose will be the prefix.
Stephen, you say this:
"If you choose to launch a Project/Folder/Task from a Blueprint you can specify whether you want the assignees of Tasks to be notified in their inbox when it's created. Regardless if you choose to notify assignees, they'll still have access to the newly launched items."
...but I don't see how to do this. Whenever I duplicate a blueprint and create a live project, no one gets notified either in their Wrike Inbox or via email.
Scott Henderson Arizona Community Foundation azfoundation.org
@Joelene, I think I understand what you're looking to do. I'm wondering to avoid subtasks here could the main task be the Project, and the now subtasks be tasks? I'm just asking as often set 'main' tasks as tasks while they're probably best suited as the Project. Otherwise this is a perfect place for this feedback as it's where the Product Team review ideas and suggestions, so thank you.
@Marj, I've raised a ticket for someone to take a look at this behaviour.
@Scott, you should see the below option in the options window when 'creating from Blueprint':
@Marj, the prefix issue should be fixed now, thanks for raising! 🙌
I submitted the comment to add suffixes (instead of prefixes, meaning to be able to choose one or the other) a long time ago, because we have the same issue: Projects are created from templates that have the same generic task titles. In order to differentiate when you look at e.g. a report you would not immediately know which specific project the tasks belongs to unless you add the prefix. Prefixes were often so long that you had to scroll to the end in order to see the generic task title. So task title followed by the project name would be ideal for us.
We need mass editing for tags, folder and projects settings.
Hi Angi, it would be great to hear a little more about the mass editing options you'd suggest. The best place to do this in the Product Feedback forum. Make sure to search for existing requests and if you can't find one to meets your requirements you can post your own request. Our Product Team has direct exposure to the ideas posted in that section 👍