Automation to only create an issue for the newly selected value and not the other values

[Adriene Howard-South]

I have a multi-select called Goals.  In that, there are several goal options.  I am wanting to monitor that field and if a new goal is selected, it automatically creates a child issue type for that particular goal.  Each goal in that multi-select is a specific issue type for me.  However, the automation is not just looking at the newly added goal and creating the issue for that, its creating an issue (duplicate) for the other goals that were already selected prior to me selecting a new one.  So I'm ending up with a lot of duplicate child issue goals.  How can I get it to just look at the newly created one?

Here is what I am doing now.  I have a branch for each goal type. 

[Rebekka Heilmann _viadee_]

Hi @Adriene Howard-South and welcome to the Community,

you could try the Smart Value {{addedFieldChange.values}} -> Automation smart values - issues | Cloud automation Cloud | Atlassian Support

Just add a "Log action" and check if that returns you the values you are looking for :) 

However, you would probably need to branch over that values List (over the smart value) rather than the current issue, as you want to create an issue for each new value, correct?

BTW, this is an excellent example of a great question when it comes to description and details :) Well done!

[Adriene Howard-South]

Yes, I want to create an issue for each new goal.  So how would that work?  So instead of choosing Current Issue in the branch rule Type of Related Issue - what do I choose?  I don't see a "smart value" option?  Also, do I need to create that smart value before that step?  So Goals equal step first and then recording the smart value?  Not sure how to do that either. 

[Rebekka Heilmann _viadee_]

@Adriene Howard-South it should look something like this:

However I am only getting one value with that and unfortunately I need to head out for the weekend. Getting back to you on Monday.

[Adriene Howard-South]

[Adriene Howard-South]

It's logging the value correctly but not recognizing that in the next step when I tell it to compare the second value Child Care Path and create the issue.