Support mass edit for comments
It would be helpful to allow for adding a comment to multiple tasks at once. In our workflow, what may happen is that we are tracking several assets being built. Each asset has a task associated with it. We may find that all assets have the same issue with them. Assets may be assigned to multiple people. Hence it is somewhat important that the comment get encoded in each task by way of comment.
I can mass edit status changes as well as folder/tags and assignee. But I cannot with the comments. I've hit this a few times already. I end up having to do a separate pass just to add comments, which is pretty frustrating.
Thanks!
Hi Ben! This is an interesting thought, and while mass editing comments isn't on our roadmap, I'm really interested in learning more about your workflow. What kinds of issues get attributed to assets?
I hope I can explain this well. Our assets get put into a build system. This is for a game. The assets may get rejected for technical reasons (build system rejects it). And in this case, there could be a few assets running into processing problems and would need to be reworked. Those assets will generally each be associated with a task. At times several assets are grouped under one task, for for this example let's just say it is 1:1 asset to task.
In this case, we want to reject the asset and let the artist know what the issue is. If it is the same issue, then we want to broadcast that within the comments for each task (since each task may not have the same assignee).
The other case this is done would be when the assets have passed the build system and have made it into the game. Here the artist or someone else would have to review it. So hence we would broadcast that as well via comments.
As a temp workaround, we are using tags for this. For example, we have a "Review in Build" folder for this and a "Rework" folder. But what it lacks is resolution of details. For example, for assets A and B, the "Review in Build" really would need to be something like "Review in build 175". Whereas perhaps assets C and D is "Review in build 176". So the encoding of "build 175" and "build 176" gets lost. "Review in Build" does not properly identify which build is needed to review.
Now imagine that instead of A and B for one set and C and D for another, it's 20 assets per set. It now becomes more difficult getting across that information.
Does that make more sense?
Ben, thank you, that helps! This one's tricky, and I'll make sure to update you if I have any breakthrough ideas, but in the meantime, I wanted to say I appreciate the feedback, and something that might help is trying to @mention user groups in the comments section of one task. This could work depending on how your teams are set up, since it draws the attention of a whole group at once. Happy to hear your thoughts on this, as well as learn more from other users who have a similar workflow!
Ben did a great job describing his particular workflow, but the use case here is even broader than he described. Any time you are changing the status on a task, there's a reasonable chance you will want to add a comment describing the reason for the change, and this is only more true when doing a bulk change.
For instance, consider: you're canceling a slew of tasks because the project or a feature has been canceled. So you select all the tasks, change their status as "canceled", and add a comment stating, e.g., "project canceled due to budget cuts" or "client decided feature {xyz} is not important, and this task only required for feature {xyz}"
Since we've got the ability to make bulk status change, it only makes sense that users similarly be able to apply comments explaining those mass changes.
+1 for bulk commenting
If someone submits a range of briefs that are all missing something, it would save a lot of time to make the same comment on all cases at once.
+1 bulk comments
I would like to see this feature implemented as well.
Hi everyone, thanks a lot for sharing your feedback here! Please make sure to +1 the suggestion above - this is what helps the Product team understand the popularity of the suggested functionality.
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