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; } } }

Selected fields must be empty in the cloned issue

Prabhu Chilukuri

Hi Team,

Whenever cloning a issues, following fields must be empty in the cloned issue irrespective of the Field data in original ticket that is being cloned.

1.Due date

2.Original Estimate

3.End date

4.Start Date

5.Fix versions

Is there a way to achieve this?

Accepted answers

John Funk

Hi Prabhu,

This is not possible with the out of the box Clone function. You can do that with the add-on Deep Clone. Another option is to setup an automation rule to clear the fields after the issue is created.

All comments

John Funk

Hi Prabhu,

This is not possible with the out of the box Clone function. You can do that with the add-on Deep Clone. Another option is to setup an automation rule to clear the fields after the issue is created.

Mark Segall

@Prabhu Chilukuri - You can accomplish this with automation. You can either recreate the clone process altogether with the desired fields copied over or create a rule that updates after the issue has been created:

TRIGGER - Issue Created
CONDITION (If applicable) - Whatever delineates these issues from other created issues
ACTION - Edit Issue: Add all the desired fields and simply leave them blank. The rule will clear them out.

Prabhu Chilukuri

Hi Mark,

Thanks for the response,

I am new to Automation rules. Could you please provide me the Example Automation rules for the above scenario?

Thanks,

Prabhu Ch

Mark Segall

Hi @Prabhu Chilukuri . Here's an example of how it could work:

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

clone