How to assign user to subtask based on custom field?

[Logan Reichert]

I have a set of sub-tasks for a work item that need to be assigned to a manager for on-boarding. I've setup a custom field "Manager" that is a people field. Is it possible to setup a automation that reads the custom field, then assigns the same person to a set of sub-tasks? 

Example: 

Manager : John Smith

(Rule would assign any sub-tasks that contains "Mgr - " to John Smith)

I've done auto-assign rules for individuals based on a "Flag" (The Mgr -) at the beginning of the summary for the sub-task but I can't seem to figure out if it's possible to assign based off what a field is populated with. 

Here is what I've got so far:

I tried using a smart value of the custom field for the "Assign the work item to" and then "user" but that didn't seem to work. 

[Viktoriia Golovtseva _TitanApps_]

Hi @Logan Reichert 

You're on the right track using automation with summary flags like "Mgr –", but assigning users dynamically based on a custom people field like "Manager" can be tricky in native Jira automation, especially across multiple subtasks.

If you're frequently creating onboarding tasks and assigning them to different managers, as a representative of the company I'd recommend using the Smart Templates for Jira app.

Here’s how it helps in your case:

• You can create onboarding template with specific checklists inside

• Use variables in the template (e.g. {{issue.Manager}}) to dynamically assign the corresponding manager/assignee on the issue creation

• Combine it with Jira automation to trigger the template when a new onboarding task is created.

📘 You can check out a full example here on how to organize onboarding workflows in Jira using templates:
👉 Employee Onboarding Template for Jira

[Bill Sheboy]

Hi @Viktoriia Golovtseva _TitanApps_ 

As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information, please see:

Atlassian Partners - Rules of Engagement

https://community.atlassian.com/t5/App-Central-articles/Atlassian-Partners-Rules-of-Engagement/ba-p/2899328

Kind regards,
Bill

[Viktoriia Golovtseva _TitanApps_]

@Bill Sheboy thank you, made correction in the answer

[Mikael Sandberg]

Your smart value component is missing the actual smart value you want to set. Your automation should look something like this to assign the sub-task to the manager:

[Mikael Sandberg]

Your other option is to use {{issue.customfield_11756}} to set the assignee, that way you do not have to use the extra component to create the variable.

[Logan Reichert]

Would using {[triggerIssue.customfield_***}} make a difference than using {{issue.customfield_***}}? 

[Logan Reichert]

I've tried both the Variable method and the just setting the assignee as the custom field value but I'm getting a "Issue was already unassigned" from the audit log.

 

This is what I had when testing it 

I had {{issue.customfield_11756}} in these screenshots