nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation should not work for cloned one

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

Accepted answers

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

All comments

@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

Screenshot 2022-10-31 at 09.52.57.png

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

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

Hi @Ismael Jimoh .

Tried it ..But it is not working.

Can you please help me

Hi

Thanks for your reply

Can you please check my below comment .

It's not working

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

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 ..

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server