How to automate assignee based on project and assigneebyrole

[Allison Mease]

We are streamlining our workflows so that all related products use the same scheme and workflow. I need to auto assign tickets in one project using the data on the individual ticket for assignee (by role) from the JIRA tracking and estimation plug in. I need to auto assign tickets in a different project to specific named users. 

For the assignee (by role), I know that you can do a post function on the transition, but I am unclear how you can apply this to just one project. So, I am trying to use the automated rules to accomplish this. I cannot figure out how to use automation to set assignee based on the values set on the individual ticket in the plug in instead of the project role. 

Has anyone else encountered this?

[Vitalii Rybka]

Hi @Allison Mease,

Welcome to the community! You can definitely achieve this with automation rules. Here's how to handle both scenarios:

For Project-Specific Role-Based Assignment:

Create an automation rule with:

1. Trigger: Issue created/transitioned
2. Condition: Project equals "Your Project Name"
3. Condition: Check if assignee by role field has value
4. Action: Assign issue using smart value from the plugin field

Smart Value Approach: The tricky part is extracting the user from your "assignee by role" plugin field. Try:

• {{issue.customfield_XXXXX}} (replace XXXXX with your plugin's field ID)
• Look at the field's JSON structure in automation logs to see the exact format

For Named User Assignment (Other Project):

1. Trigger: Issue created
2. Condition: Project equals "Other Project Name"
3. Action: Assign issue to specific user

Debugging Tips:

• Add a "Log action" to see what values the plugin field returns
• Use "Advanced" field conditions to check field contents
• The plugin might store user keys, display names, or account IDs differently

Alternative: You could also use post-functions with project conditions in your workflow transitions.

Which specific "assignee by role" plugin are you using? That would help with the exact smart value syntax.

Need help with the specific automation setup? Feel free to DM me

[Allison Mease]

Thanks so much for the quick response! Glad to know this can be done. We are using Tracking and Estimation for JIRA Cloud:

[Vitalii Rybka]

Hi @Allison Mease,

Perfect! For Tracking and Estimation for Jira Cloud, here's the specific approach:

Smart Value for Assignee by Role Field: The plugin typically stores role assignments in a custom field. Try these smart values:

• {{issue.customfield_XXXXX.accountId}} - if it stores account IDs
• {{issue.customfield_XXXXX.name}} - if it stores display names
• {{issue.customfield_XXXXX}} - to see the raw field structure first

Finding Your Field ID:

1. Go to Jira Settings > Issues > Custom Fields
2. Find your "Assignee by Role" field from the plugin
3. Note the field ID (customfield_XXXXX)

Automation Rule Setup:

Trigger: Issue created/updated
Conditions: 
- Project = "Your Project Name"
- Assignee by Role IS NOT empty
Action: Edit Issue
- Assignee: {{issue.customfield_XXXXX.accountId}}

Debugging Steps:

1. Create a test automation with just a Log action first
2. Use {{issue.customfield_XXXXX}} in the log to see the exact data structure
3. Based on the output, adjust your smart value syntax

Common Patterns for T&E Plugin:

• The field might return an object with user details
• You might need .user.accountId or similar nested properties

Try the log action first and share what structure you see - that'll help pinpoint the exact smart value syntax!