Automation should not work for cloned one

[Aswathi D]

Hi ,

I have an automation like , if an issutype = story is created  then the description should be " XXX" .

But my problem is when a story with description " YYY " is cloned then the cloned story is overwritten by XXX . But what I expect here is YYY in description.

How can I avoid this ? I don't want this automation to be performed in cloning 

[Gaurav · Accepted solution]

Hello @Aswathi D 

As per my understanding of the use case, the description of the cloned issues should not be updated.

For this, you can add an 'if/ else' construct, check if there are any links of the type, 'clones/ is cloned by', are present, then do not update the description; else update the description as required.

Please let me know if you need any help with this construct.

Kindly accept the answer if this helps.

--GG

[Aswathi D]

Hi 

Thanks for your reply 

Can you please check my below comment .

It's not working

[Gaurav]

Hello @Aswathi D 

Here is what is happening:

• A story is created manually, ABC-1
• Automation triggers updating the Description to 'XXXXX'
• The story is then cloned, creating a new story, ABC-2
• The Automation does not update the Description but since it is a clone of Story ABC-1; the description is copied giving the impression that it is updated by Automation

As the cloned story needs a different Description, please update the Automation rule to add the relevant description, when the new story has a link of 'clones/ is cloned by' type.

Please share if this helps the scenario.

Kindly accept the answer if this helps.

--GG

[Aswathi D]

Hi @Gaurav ,

Let me explain once again what I need .

When the story is cloned I dont what a new description, but the exact copy of cloned ticket ( meaning automation shouldnot trigger in cloning cases)

What I understood from your explanation is , to give a new description when a story has link type ..right?

But I need the exact copy ..not a new one ..

[Gaurav]

Hello @Aswathi D 

I tried to create the Automation on my end. Please refer to the below screenshot of a rule which should work for the use case.

Kindly check and share your feedback.

--GG

[Aswathi D]

Hi 

 @Gaurav ,

Thanks for your continuous support .

When I clicked on publish changes , I am getting the below error ..Am I doing anything wrong ?

---

[Aswathi D]

[Gaurav]

Hello @Aswathi D 

The action step (pencil icon in blue) of the Automation rule is misplaced. This needs to be placed under the If block where you have the 'Plus icon in Grey'.

Please update this and share the feedback.

--GG

[Aswathi D]

Hi @Gaurav 

Unfortunately ,it is not working ..still the description is not getting cloned .

[Gaurav]

Hello @Aswathi D 

This is strange!!

Could you please share the Description which is showing up on the Clones Issue? Is the description of the clone issue matching the description defined in the Automation Rule?

Also, please share the Issue Links on the clone issue and the audit logs for the Automation rule.

These will help in identifying the problem here.

--GG

[Ismael Jimoh]

@Aswathi D cloning an issue is the same as creating an issue in JIRA with just specific fields being auto-populated. It is a new independent issue as far as the application is concerned.

A possible workaround for you would be to update your automation and check for the issue link clones. If this is not true then run your automation.

In your condition you can use Related issues -> clones -> Are not present see image

This should ensure that your cloned issue doesn't trigger the rule.

[Aswathi D]

Hi @Ismael Jimoh .

Tried it ..But it is not working.

Can you please help me