Allow changing of the rule actor in cloud
Considering that this has been in backlog for over a year, I hope it hasn't been forgotten. As a designer of automation rules for multiple project owners, our use case creates sub-tasks (after conditions are met). It would be ideal if those sub-tasks inherit the original Reporter from the parent issue. However, when the automation rule executes, the newly created sub-tasks reflect the rule "actor" as the Reporter. Which means all reporting on that issue, goes to a single person (right now, that's me....so you can understand why this is a problem). When issues are updated, the real Reporter is in the blind. Multiply that problem across multiple projects with 'me' as the new reporter (due my designation as the actor), and it creates a huge communication gap. The problem can be solved by reassigning each automation rule to separate actors, but it only spreads the same problem.
Can the actor selection be adjusted to 'inherit' from the Parent? (for my particular use case). If not, can the actor be changed to a service account? I've tried the latter, and get an error that the new actor (service account), doesn't have permission to 'edit' an issue. For this as a workaround, what are your thoughts/recommendations?
This is something we plan to add but It's actually a fairly complex feature to implement since it requires being able to execute rules as other users - just changing the name of the addon system user isn't possible unfortunately.
At the moment we've got quite a few higher priority items in our backlog at the moment so it will be a while before we can get to this, but we'll let you know when we get a chance to work on this.
Is there any expected date this will be implemented in Cloud? The default automation rules have this ability and leads me to have the preference of using default Automation (since I can change the name).