Change the reporter from Automation for Jira to a user by an automation

Elif Alverson April 20, 2023

Hello,

I have this automation below which creates subtask based on the field location status . It works fine however I would like to add another step/s to change the reporter of a sub task from "Automation for Jira" to assignee of the parent ticket. How can I accomplish that? Is it even possible? Thank you.

Screenshot 2023-04-20 at 12.23.03 PM.pngScreenshot 2023-04-20 at 12.23.07 PM.pngScreenshot 2023-04-20 at 12.23.11 PM.pngScreenshot 2023-04-20 at 12.23.17 PM.pngScreenshot 2023-04-20 at 12.23.31 PM.png

1 answer

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2023

Hello @Elif Alverson 

Yes, if the Rule Actor has the permission in the project for changing the Reporter field, then you can change the Reporter on the issue you are creating to match the assignee of the parent issue thus.

Screen Shot 2023-04-20 at 9.44.54 AM.png

However, if the parent issue has no assignee then the rule will fail because the Reporter can't be empty.

So you may want to add a separate step in the branch to check that the parent has an Assignee and then Edit the subtask just created.

(Disregard that I used Component for my branch.)

Screen Shot 2023-04-20 at 9.50.40 AM.pngScreen Shot 2023-04-20 at 9.51.17 AM.png

Elif Alverson April 20, 2023

@Trudy Claspill , thank you for your response. The tickets are assigned to the team lead automatically so there are not ticket in unassigned state. I added the steps you provided above however not still does not work. Here is the message I got. I am an project admin but it says the issues cannot assign to me. ????

Screenshot 2023-04-20 at 1.30.55 PM.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2023

Please show us your automation rule and the details of the steps you added.

Elif Alverson April 20, 2023

I am getting this error message below and here are my automation steps;

Screenshot 2023-04-20 at 2.42.34 PM.pngScreenshot 2023-04-20 at 2.39.27 PM.pngScreenshot 2023-04-20 at 2.35.00 PM.pngScreenshot 2023-04-20 at 2.35.33 PM.pngScreenshot 2023-04-20 at 2.36.27 PM.pngScreenshot 2023-04-20 at 2.37.58 PM.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2023

You need to remove the Reporter field from the Create Issue task.

In the Edit Action you should be using triggerIssue, not parentissue

Elif Alverson April 20, 2023

I did ( please see below ) the changes you requested. But this time my subtask's reporter is still "Automation for Jira". It did not changed to me. And it shows success.

Did I miss something?

 

Screenshot 2023-04-20 at 3.09.13 PM.pngScreenshot 2023-04-20 at 3.09.22 PM.pngScreenshot 2023-04-20 at 3.09.27 PM.pngScreenshot 2023-04-20 at 3.09.37 PM.pngScreenshot 2023-04-20 at 3.07.39 PM.png

Elif Alverson April 20, 2023

It does not work as expectedbecause Parent Issue is picked as Current issue?

 

Screenshot 2023-04-20 at 3.17.23 PM.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2023

Oops, I gave you some invalid guidance.

You have two options. Use only one of these options.

Option 1:

If your trigger issue will always have an Assignee, then you can set the Reporter field within the Create Issue task.

Also note that smart values can be case sensitive. You need a capital "i" for "issue" in "triggerIssue"

{{triggerIssue.assignee}} not {{triggerissue.assignee}}

With this option you don't need the Condition and Edit steps after creation of the subtask.

---

Option 2:

If there might be a case where the trigger issue does not have an Assignee, then don't try to set the Assignee in the Create Issue action. Instead, after creating all the subtasks, check if the trigger issue assignee has a value and if so then update the Reporter on all the Subtasks.

Screen Shot 2023-04-20 at 12.28.36 PM.png

Like Elif Alverson likes this
Elif Alverson April 20, 2023

@Trudy Claspill , it worked. Thank you so much! You are awesome!!!!!

Like Trudy Claspill likes this
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2023

Happy to help ;-)

Suggest an answer

Log in or Sign up to answer