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 of Stories and CLONEs

Cyril James_leu7ov

Hello Friends, I have automation set up so that when someone creates a new story, the story description is pre-populated with the info for required information that is needed to groom the story. Acts like a story template.

However, if we take an existing story and CLONE it, the existing story description is erased and replaced with the pre-populated description from a template so we are starting form scratch.

How can we exclude the pre-populated story description when cloning.

Thank you!

Accepted answers

All comments

Trudy P Claspill

Hello @Cyril James

When you clone an issue do you apply the "CLONE - " prefix to the Summary?

Please show us the automation rule you are using to replace the Description text.

I suspect that your issue is triggered by Issue Created. You will need to add some condition after the trigger to detect that the issue is a clone. You might do that by checking the Summary field for the "CLONE" prefix. Another way would be to check if a "clones" link exists in the new issue.

Screen Shot 2023-03-27 at 4.08.30 PM.png

Bill Sheboy

Hi @Cyril James

One way to do this is to add a related issues condition to exclude cloned issues, as below:

trigger: issue created
action: re-fetch issue (Including this is a good idea when using the issue created trigger, as it can occur so quickly that the data is not available yet.)
related issues condition:
- Related issues: Linked issues
- Link types: is cloned by, and clones
- Condition: Are not present
...continue with your rule

If this does not help, pleases post images of your complete rule and audit log details. This will provide context for other suggestions. Thanks!

Kind regards,
Bill

Cyril James_leu7ov

Thank you! When I say clone, I mean open story A, go to 3-dot menu, select CLONE, in a few seconds, cloned story is created. I get a little dialog box in the lower left on my screen that says, click here to review cloned issue. Its this action that removed the cloned story original decription

Trudy P Claspill

Hello @Cyril James

You said:

I have automation set up so that when someone creates a new story, the story description is pre-populated with the info for required information that is needed to groom the story. Acts like a story template.

I am asking to see that automation - the one that fills in the Description. Is that template text showing up in the Create Issue dialog, or does the original issue get that template text after it is saved?

Cyril James_leu7ov

Trying this now....

Cyril James_leu7ov

Hi Trudy, this works. Per your post above, if I clone an issue, the issue description is not over written. Great news!

Can we enhance this in two ways.

#1, If I hit the Create Issue Button, enter a Summary and enter a description, it gets over written by my rule, and inserts my automated description update. Thoughts on this. I wish I could append my issue description to what ever the person trying to create the story entered into the description. Does this make sense.

#2. Can I format the fonts when through automation, I create issue description.

Thank you

Soumya Hatti

Hi,

I have similar issue where after clone the description get's replaced with the template rather than retaining the original ticket description. I tried above steps but still unable to fix this. Can someone please help?

Bill Sheboy

Hi @Soumya Hatti -- Welcome to the Atlassian Community!

As this is an older thread, I recommend creating a new question and perhaps including a link back to this one. That will ensure the maximum number of people see your question to offer suggestions.

When posting your question, remember to include:

your Jira version: Cloud, Server, or Data Center
the type of project: company-managed, team-managed, etc.
describe the problem your rule is trying to solve
an image of your complete rule
images of any trigger / actions / conditions / branches not working as expected
an image of the audit log details showing the rule execution
explain how the rule is not working as expected, and what leads you to believe that

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation