Hi,
I try to use the {{initiator}} smart value to retreive the initiator of the issue, in automation rule. It's not working for me.
My rule is triggered by webhook and I would like to who trigered it (from action button )
So I tried to write the {{initiator}} to the log and below is what I get in the audit log - empty value.
Any idea how to retrrive the initiator in this case ?
More details : The rule creates new issue and I need the reporter to be the one who trigered the action, I did not find a way to do so. The options to set the reported from the create action do not fit
So I try to set it with smart value.
Any idea will be appreciated.
Thanks, Gal.
Hi @Gal Fatal
As your rule trigger is Incoming Webhook, that could be from anywhere, and so I expect {{initiator}} is not defined in that case.
What is causing that webhook? And is there information in the message which could be used to determine the user needed?
Kind regards,
Bill
Good point Bill. I did not come back to that point after seeing the error message. It will be good to understand the webhook requirement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The idea of the Webhook is to let the user create bug from a user story.
The automation rule update some fields with defaults. copy some fields from the user story and create a link between the new bug and the user story.
So it's a quick way for the user to create a bug related to specific user story.
and I am looking on a way to set the reporter of the new bug to be the one who clicked on the automation in the actions menu, the one that is now loged in and intiated this action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm...if a user selected and ran a manually triggered rule from the Actions menu, the {{initiator}} should be that user.
I am still not understanding what is generating the incoming webhook, as that would not be needed based on what you described. Instead only the manually triggered rule would be needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Gal Fatal , I wonder if it is related to the ongoing issues with Automation. https://jira-software.status.atlassian.com/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, one comment here. You mention "I try to use the {{initiator}} smart value to retreive the initiator of the issue...",but to be clear {{initiator}} refers to the user triggering the rule not the reporter of the issue for which you would use {{issue.reporter}}.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jack Brickey thanks for your assistance.
{{issue.reporter}} gives me the reporter of the existing issue, not the new one.
Since the creation is executing by "Automation for Jira" which is always the actor in my case, the reporter becomes "Automation for Jira".
Here is the use case:
1. User A creates a user story. He is the reporter.
2. User B would like to create a bug related to this user story. So he goes to "Actions" menu and run automation we created, that creates a new bug and link it to the user story issue. (Create Linked bug")
Now, I would like to set the reporter of the new bug to user B. because he executed the automation to create the bug.
but now its "Automation for Jira" and I do not find a way to set it to user B.
if I try {{issue.reporter}} - it gives me user A. I need the one who clicked on the automation, user B.
That's why I tried the {{initiator}} but it does not work
Any thoughts ?
Thank!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Gal, the details help. For your Manually triggered rule can you check to see if the Actor is set to "user who triggered the event".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jack Brickey sounds like a perfect solution. but when I try I geth error
"the selected trigger requires the actor to be set to a user"
:( :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Gal Fatal , sorry for the delay in getting back to you. I have been off on other errands. I would like to test a theory out and was wondering if you could either clone or reconstruct that rule from scratch and see if that error message persists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.