Automation - Set Issue Value based on project of a linked issue

Celina Kincaid

Can someone please help me create an automation rule based on the project of a linked issue?

• MAIN-123 ticket has a relates to link with ticket CLIENTA-124 and ticket CLIENTB-223.
• MAIN-123 has a CLIENTS field with checkboxes for each client.

What I would like for the automation rule to do:

• For MAIN-123, 
  • For the CLIENTS field, check ABC because that is the name of clientA
  • also for the CLIENTS field, check BBB because that is the name of clientB.
• I understand I will have to define the correlation between project key to client name somewhere.

Can someone help --- MUCH APPRECIATED!

Bill Sheboy

Hi @Celina Kincaid 

What have you tried thus far to solve this?  If you have a rule that is not working, please post images of the complete rule, the audit log details, and explain what is not working as expected.

If you have not yet started a rule, some suggestions to get you started are:

• Here is an overview of how rules work: https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• Your planned rule will use issue data from different projects, and so needs to be global or multiple-project in scope.  A rule like that will be defined at the global administration level rather than at a project level.  You appear to be a Jira Site Admin, and so you can do that.  Please look here to learn more about rule scope: https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/#Edit-the-details-of-a-rule
• When do you want this to happen?  For example, when an issue link is added?  Knowing that will help you decide which rule trigger to use: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/
• The mapping you describe of project key to client name (and value in your custom field) could be done using a Lookup Table: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798
• After finding the client names, you may add the values to the custom field in several ways, such as using advanced edit with JSON to prevent overwriting existing values: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-select-custom-field

Please try those sources to get started, and if you run into challenges please post an image of your rule and describe what is not working as expected.

Kind regards,
Bill