We’ve created a custom rule that uses the “Run script” external action.
Within this script, we’re using the storiesApiInstance to create a comment on the task. It all works, but it also adds the rule creator (me) as a collaborator (follower) on the task as a result of the comment being added (even though the comment is coming from “Asana”.
Is there any way to prevent this? I realize I could create the rule with some “dummy” user, but that’s not ideal either. I realize I could also subsequently remove myself as a collaborator, but I’d prefer to not add that sort of logic (since I’d need to check if I was previously a collaborator in the first place).
Either way, ideally the rule creator wouldn’t be added as collaborator, just because their rule action of “Run script” added a comment (that isn’t even authored by them).
That’s normal, the code is ran on the behalf of the user so you appear to be the one who did the action.
Creating the rule as a dummy user (we have a Yeti user in our instance for example) would be my go to choice
Right; but why would that user be added as a collaborator? That doesn’t make sense to me.
If you find a task and comment on it, you are added as a collaborator. It makes sense, you join the conversation.
Oh right, sorry, I was thinking the point was the act of using a custom script was doing that, but missed the actual point: it’s the action of adding the comment - so yes, make sense given how Asana normally behaves.
Well that’s the case: anything the Custom Script does (post comment, complete task…) will be done “as you”
But is that true, @Bastien_Siebman? @FreshyJon indicated that was not the case - he said it was recorded in the story as being from Asana, not the user name:
So now I’m confused.
Oh I am confused as well then 
I just checked, and I was wrong → Asana is the author of all the actions
1 Like