918
Dynamic assignee for Automations
in progress
Jo Martin
It would be great if I can choose "me mode" in an automation.
Here's my use case:
There are a new feature with 20 tasks. All in To do status. Developers decide which one they want to work on.
So I want to make an automation:
When status changes from to do to any, Then change assignee to "currently logged in user". The user who changed the status.
Log In
Zach - ClickUp
Hey all,
I've tried to capture all the feedback here and I've come up with the following list. Let me know if there's anything critical I'm missing. I put this in no particular order of importance:
- Task Assignee
- Task Creator
- Watchers
- Assignees
- People custom field
- Person who triggered the automation
- Time Tracked for X person (assignee or people custom field)
Quick explainer video (UDPATED): https://www.loom.com/share/092d7de04cc04ea398784f0e11e90f31
pixojoy
Slightly related, there are requests on this linked post for custom item types being a trigger inside of automations. Wanted to bring that over here since you've been actively working on automations Zach - ClickUp https://clickup.canny.io/feature-requests/p/custom-item-types-instead-of-only-tasks
R
Rebecca Julius
The one I really want is a two part feature request, but I want to trigger on a comment being added (with a condition of it being in a certain status), and then I want to assign to the person who commented. I don't know if it's useful to add "person who last commented" to your list without the trigger feature though?? Thanks for thinking about it!
Pete Jackson
Rebecca Julius: the proposal here to assign to the user who initiated the automation already handles your use-case as the trigger would be the comment
R
Rebecca Julius
Pete Jackson: I don't see "comment added' as a current trigger. Am I missing it?? Thanks!
A
Angel Carrier
Dynamic Assignee (It would be nice to have the option of setting the automation to set assignee by who triggered the task or by the contents of a custom field)
Zach - ClickUp
Hey all, can I phone a friend?
I'm trying to figure out the name for "person who triggered automations" but can't think of a great 2 word name...any suggestions? Here's what I've come up with:
- Automation Initiator
- Process Starter
- User Triggered
- Trigger-Based Operator
- Triggering Automation User
Roberto Gálvez
Zach - ClickUp: Process Initiator?
Eric Cote
Zach - ClickUp: Does "Initiated By" or "Triggered By" work?
Yisroel Falkowitz
Zach - ClickUp: My vote: User Triggered
M
Michelle Lawless
Zach - ClickUp:
- Action Initiator
- Action Owner
- Initiating User
Markuss
Zach - ClickUp: I'm sorry, but all of those sound too cumbersome. You basically want to make it plain that the task will be assigned to the person moving / affecting the task / ticket.
What about: Active User
C
Cheyenne Cattanach
Zach - ClickUp: Triggered By - Matches format in data sets from other applications (Created by, Modified By, etc.)
Ross McConeghy
Zach - ClickUp:
- Initiating User
- Triggerer
- Triggering User
Nicole Bandes
Zach - ClickUp: Is that different than who created the Automation? If not, since you already have Task Creator, it could be Automation Creator. If so, I agree with Triggered By.
C
Cameron Blakey
Zach - ClickUp: User Who Triggered Automation
E
Elizabeth Brucker
Zach - ClickUp: Activator or Trigger activator?
E
Elizabeth Brucker
Activating user?
Eric Demerath
Zach - ClickUp: I like "Automation Initiator" Or "Initiating User"
Destiny Pidgeon
Zach - ClickUp: I think Triggered By is the most intuitive
Anne-Marie Wood
Zach - ClickUp:
Current User
OR
You with an emoji finger pointed out towards the person making the change :)
Jacob Forrest
Cheyenne Cattanach: This makes sense to me. Created by 👍🏼
Jacob Forrest
Zach - ClickUp: "Create" is the term ClickUp uses, so "Created By" or "Task Creator" makes sense to me.
J
John Sanchez
Zach - ClickUp: Modified by
Patrick Kofler
Zach - ClickUp: "Triggered by" is the way to go
James Wooldridge
Zach - ClickUp: Trigger User or Triggerer
N
Ny Nguyen
Zach - ClickUp: Triggered By
pixojoy
Zach - ClickUp: Activated By or Triggered By
Ben Porter
Zach - ClickUp: Triggered by or Triggering User
Scott Carpenter
Zach - ClickUp: I like "Triggering User" the best, but I think that "Triggered By", "Triggered By User", or "Automation Initiator" would work as well.
Sascha Kirchdörfer
Eric Cote: Yes, I actually us wanted to suggest "Triggered By" and I'm using these terms all the time.
Andrea Leick
Zach - ClickUp: I go for User Triggered 👌
Paul B
Zach - ClickUp: Triggered by
A
Alex M.
Zach - ClickUp: Autor ;)
A
Alan Ballany
Zach - ClickUp: "Triggered By"
Brian Said
Zach - ClickUp: Triggered By
J
James Jensen
Zach - ClickUp: AI also suggested "Activator", "Invoker"
Pablo González Day
Michelle Lawless: Initiating User is a good one!
Pete Jackson
Zach - ClickUp:
- Triggered by - follows well established + familiar naming conventions (e.g. Rails ActiveRecord). The context + icon clarifies this is a user
- Initiator / Automation Initiator - fits better in existing context + follows "task creator" and "watchers" convention
Zach - ClickUp
Bingo! I think that's the one ✅
Triggered by
P
Peter Melis
Hi Zach! Great stuff thanks! Maybe on the nice to have list: automatically assign to the assignee before the current assigne (so assign back)
Ben Porter
Zach, one that's not on your list that would be valuable is to set List Owner as the assignee.
Then by default you can have any new tasks on a project go to the project manager by default.
For instance, if other stakeholders request an action on a project, they don't have to choose who to assign it to. It can automatically be routed to the Project Manager for them to assign to their team.
This would also be a real functional reason to use the List Owner (which is currently a very niche feature)
pixojoy
Ben Porter: I'm not a ClickUp employee but is this the automation that you're looking for? This can be set up per List in its automations. Or do you mean for "List Owner" to be a custom trigger for automations, so that you don't have to manually set up the Assignee inside of automations for each List? I want to understand fully.
Ben Porter
pixojoy: Right, it is possible to create a new automation for each list, but the fact that you have to change it for each list is my point.
With what I suggest, you could create a single Folder- or Space-level automation to "assign newly created tasks to List Owner," then set the list owner as you create projects without having to think about the automations.
The list owner is now prominently shown in the Folder overview, while the automation is hidden in a separate menu.
pixojoy
Ben Porter: Oh, I see now. Thank you for elaborating on that idea. I think this would be a fantastic addition.
Zach - ClickUp
Quick demo update for y'all! We're making progress
Perry Wirth
Zach - ClickUp: Very cool feature!!! This will be useful on some lists of ours!
Yisroel Falkowitz
Zach - ClickUp: Massive
E
Elizabeth Brucker
Zach - ClickUp: This is SO needed!! Being able to assign/comment by automation based on a custom field will be huge.
pixojoy
Zach - ClickUp: Letsgooo!
Jarod McPherson
Zach - ClickUp: yup- that would be a hella helpful feature!! :)
Jake Spirek
Zach - ClickUp: awesome!
R
Ruud
My challenge currently is to ensure someone filling in the form being added as watcher :)
Would be nice if this can be added to the automation to automatically assign or add watchers, to set it to 'task creator.
Also at the point to assign a form to someone, and of course in automations as well.
Theoretically (but maybe unrelated to this ticket) is that I can also automatically share a task publicly with the person filling in the form, but taht might be a feature in itself.
J
Jay Sublett
Ruud: Same! Can this be done?
Zach - ClickUp
Ruud: We should be able to capture this
Ruud
Zach - ClickUp: Sounds good!
Tim Jasper
Zach - ClickUp I'm trying to cover a scenario where an assignee simply unassigns themselves from a task. My preference is to be able to lock an assignee in place for a task, however in the current absence of this functionality, do you foresee a way with automations to reassign the task back to the user based on a re-assigned people field. eg (with assignee Tim ) when we assign a task we could set the assignee and custom people field to "Tim'. If Tim then unassigns himself , the automation would look to the hidden people field and simply reassign the task back to Tim. (or can clickup please allow assignee to be locked https://clickup.canny.io/feature-requests/p/lock-task-assignee 🙏 )
Zach - ClickUp
Tim Jasper: Hmm, I'm sure this release could help you somewhat achieve what you're looking for, but not fully. I'm sure you've considered this, but you can change task permissions to prevent editing status.
Zach - ClickUp
Merged in a post:
Variables in Automation logic
J
Judson Wells
Working with a larger team, creating an automation that assigns a -particular- employee doesnt always work. We need an option for logic that allows to change assignees to a value of a field, not to a particular team member. this is just an example, but placeholder variables would make automations far more compelling and capable for scaled teams.
Load More
→