Edit field of target issue via automation

[Marcel Jünge]

Hi,

i am currently working on an automation rule with no success:

Situation:

• We use a JSM Portal for requesting licenses.
• In the request an object in JIRA Assets can be selected (Software) and the amount of licenses is entered.
• A jira project exists that has issues corresponding to the assets objects (Difference: Instead of "Amount of licenses" it is called "Number of licenses"

Automation: 

1. Whenever this request is created the automation should look up issues in a jira project "Key "SC" with the same name as the selected object in the request (e.g. Selected object = Software A and correspondng issue in JIRA project = Software A).

2. The automation then should add up the numbers in the fields "Number of licenses" (Jira issue) and "Amount of licenses" (ITSM Portal request) and update the JIRA issue field. 

Maybe somebody can help me.

Thx. 

[Evgenii]

Hi, @Marcel Jünge 

Weird logic, don't understand why are you looking for similar issues, and try to change them, if you want to edit Assets object.  But maybe you have some internal logic that describes it. 

Anyway, this solutin can help in your case. Create new automation rule:

Trigger: Issue created (scoped to your JSM project)
Action 1 - Look up issues:

project = SC AND summary = "{{issue.customfield_XXXXX.label}}"

Replace customfield_XXXXX with your Assets object picker field ID. The .label gives you the object name like "Software A".

Action 2 - Branch: For each looked-up issue
Action 3 (inside the branch) - Edit issue:
Select field: Number of licenses
And set value, like:

{{#=}}{{issue.Number of licenses}} + {{triggerIssue.Amount of licenses}}{{/}}

Small notice - if fields store decimals like 5.0, append .asNumber to both smart values

[Evgenii]

Set rule project scope to multiple projects (JSM and Software). In trigger action add condition to check, that issue was created in JSM project.

[Marcel Jünge]

@Evgenii First of all thanks for your answer. My Question: Which of these options should i use and how?

[Marcel Jünge]

Like this?

[Evgenii]

No, just use branching, select issues by JQL in this branch, and work with them. Don't use lookupIssues