Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is it possible to change the "Actor" of the automation rule to be the current user?

The activity log makes it look like the person who created the rule was responsible for the automation event.  Is there a way to set that value equal to the current user, so we can more easily trace who triggered the event?

35 answers

I would also like this feature.

This looks to have been completed in the automation tool

 

It, is really working out for our needs

 

Automation rules - JIRA 2020-10-11 12-20-43.png

I'm running the latest plugin version for server, and that option does not exist :(

Like # people like this

Does the change only affect the Cloud version - and not Data Centre?

Any updates on this one?  I have an automation rule that adds a comment to a ticket based on a transition.  The comment is currently being made by a generic user with the unfortunate byproduct being that the Agent is notified as having a Customer comment on their issue

 

If the rule Actor was able to be set to CurrentUser I beleive this would fix my issue

Unfortunately this hasn't hit our roadmap yet (despite its popularity). Our current focus has been on Ease of use and scalability and reliability. We hope to pick up some capability stories soon but I can't make any promises on dates. Sorry. 

Like Deniz Ozkaynak likes this

"Automation for Jira" programmers team doesn't look so agile. 2,5 years have passed and such an important function has not been done. A typical Atlassian ecosystem problem 

ditto

we would need this too.

Hey Mick,

 

Unfortunately we don't support this yet but we are tracking this at - https://codebarrel.atlassian.net/browse/AUT-97

There are a few complications with around permissions and in particular permission escalations that we need think through.

We are working on some high priority items at the moment so I can't make an promises on dates for this. Sorry.

 

Cheers,

Nick [Code Barrel]
Co-founder

Need to put "assignee" on a rule please ! 

+1 urgently needed!

+1 Vote! 

YES!  Please get this implemented in Jira Server. 

Thanks,

Mark

this is working in jira cloud

My company would love https://codebarrel.atlassian.net/browse/AUT-97 completed as well.

The common Jira workflow post-function "Assign the user to the current user..." really messes with Jira Automation Plugin because it will always assign the issue to the rule actor. If the rule actor was the current user, this wouldn't be a problem.

0 votes

Guys, our team also needed this feature, but as we couldn't wait, we used an alternative approach. You may find this approach useful, although it requires some efforts (sometimes very little) to get it working.

So, the idea is that we developed a custom automation action to run Groovy scripts!

It is fully compatible with the built-in triggers, you can use this action in any automation rule.
In the Groovy script you can implement any logic and you have full control on the identity of the user who executes that logic.

For example, if you want to add a comment to one or a set of issues, run this Groovy script:

import com.atlassian.jira.bc.issue.comment.CommentService
import com.atlassian.jira.bc.issue.comment.CommentService.CommentParameters
import com.atlassian.jira.component.ComponentAccessor

def author = devops.committerByUsername // <-- define the comment creator here

def commentService = ComponentAccessor.getOSGiComponentInstanceOfType(CommentService)
issues.each { issue ->
 def commentInput = CommentParameters.builder()
  .issue(issue)
  .body(devops.comment)
  .created(new Date())
  .author(author)
  .build()
 def commentResult = commentService.validateCommentCreate(author, commentInput)
 if (commentResult.valid) {  commentService.create(author, commentResult, true)  auditLog.addAssociatedIssue(issue)  auditLog.addAssociatedUser(author)  auditLog.info("Comment added to ${issue.key}")
 } else {
  throw new IllegalArgumentException(commentResult.getErrorCollection().toString())
 }
}

As you see you can specify the user in line 5. (Our use cases are related to Version Control System changes, so we use the committer actor parsed from the Git/SVN/Mercurial log.)

The drawback is that you need to write the action's logic in Groovy. But we have quite a few sample you can use as starting point to automate comments, worklogs, transitions and status updates, editing fields and more.

Learn more details here.

(Discl: The app was originally developed for our internal needs, but we decided to publish this as a supported Jira app.)

Me too.  

Is this feature released ??

0 votes

We definitely need this in Data Center (and Server).

This feature is in DC and Server already available. This Thread was only about the cloud version, which did not had this feature few months ago. Since Atlassian delivered an update. This complete thread is obsolete. 

 

 

Go to your automation, -> rule details -> Actor.

Hello @Bjoern Veith 

 

I don't see this feature in the server version? Are you sure is possible to select "User who triggered the event" as an Actor in the server version?

Like # people like this

@Bjoern Veith Honestly, I don't think it is resolved.

Can you attach a screenshot about the related config option (from the Server or DC version of the app)?

Something just changed because now the issue being transitioned by the automation is being re-assigned to the Actor.

+1 I really need this one

Rumor has it with tech support this is being worked on.

This feature is a must and was available in the Server Version. Please include this asap

Definitely need this one!

Hi.  +1 for this, and for voting for this.

One of the last big pieces of the AFJ puzzle to total awesomeness.

Worse for me!

I'm getting spammed by updates to cases on Service Desk as the one who initially created those cases. Then it uses my user account to change workflow states which means I'm added as a watcher of every single Service Desk ticket!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

🍻🍂Apptoberfest Update: Upcoming Virtual Events 🎉

Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...

472 views 5 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you