copying a user via automation from another issue

BEN FRIEDMAN

Hi,

the setup i have is this:

ticket A contains a custom field with value "x".

"x" is the summary of ticket B. 

ticket B has a sales rep field (user) with a "user's name".

ticket A also has a field for sales rep.

i need an automation that will run manually from ticket A, which will copy the sales rep from ticket B to ticket A. 

 

what i currently have is:

on manual triger

if ticket matches conditions

for JQL (summary ~ "x" and  issue type = ticket

  create a variable salesRep = {{issue.Sales/Account Manager.accountId}}

edit issue with JSON

{
"fields": {
"Sales/Account Manager": { "id": "{{salesRep}}" }
}
}

 

im getting the error that the account doesnt exist. 

 

any ideas how to resolve?

Bill Sheboy

Hi @BEN FRIEDMAN 

I am guessing at your rule structure a bit, so please let me know if this helps...

Create Variable can only be set and not edited yet...but, values can be preserved if you handle scoping.  Here are two scenarios:

 

• Trigger: ...
• Branch: ...
  • Action: create variable varMyVariable setting it to {{issue.key}}
• Action: log the created variable varMyVariable

In this scenario, the variable is created within the branch and so when it goes out of scope, the logged value is empty.

 

• Trigger: ...
• Action: create variable varMyVariable initialize it to "null"
• Branch: ...
  • Action: create variable varMyVariable setting it to {{issue.key}}
• Action: log the created variable varMyVariable

In this scenario, the variable is created before and again within the branch using the same name, and so the value is preserved and logged.  Please note: this works only when the branch returns one-and-only-one issue; otherwise the asychronous processing of branches creates a new variable for each issue, and so is not saved.  One-issue branches are converted to in-line code.  To ensure your branch JQL evaluates to one issue, consider if you can replace the summary match with ~ to an exact key match.

Best regards,

Bill