Post automation function for Clone workflow only

[Pulkit Gupta]

Can we add post automation function only for Clone workflow without impacting create workflow?

[Clara Belin-Brosseau_Elements]

Hello @Pulkit Gupta 

If I understand correctly, you’re trying to clone only specific issue fields, right?

 In that case, I would recommend trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You’ll be able to define which fields need to be cloned.

You can check the guide here.

The app is for free during 30 days (and it stays free under 10 users).

[Nikola Perisic]

Welcome @Pulkit Gupta by clone workflow, do you mean the copy of the original workflow? If this is the case, yes you can, since it is a different ID than the original workflow.

[Pulkit Gupta]

Yes, As the detailed usecase we want to make sure that some attributes are set to null and carried with clone.

The native clone feature of JIRA dont allow to skip attributes from cloning and was shared as an alternate to use Post Automation Workflow for resetting these attributes.

The issue was if we setup a post automation tool to reset attributes it should not impact the JIRA which are not created by Clone but are created as normal new.

[Pulkit Gupta]

Clone workflow i am referring to Native clone feature of JIRA

[Nikola Perisic]

Which attributes need to be cloned? What automation rule needs to accomplish?

[Pulkit Gupta]

We look to use the native clone feature of JIRA where it allows to clone all attributes from source to new JIRA.

While we need only the Description, program, client, subject, and qualitative metrics attributes to clone

[Nikola Perisic]

I would suggest to use the Deep Clone app from the marketplace in order to have optional fields to be cloned. This cannot be done by the native clone functionality even if you try to use the automation.