Best way of Cloning Issue Which force user to fill mandatory and replace older value

[Vikrant Yadav]

Hi Experts,

I am very confused, User is asking to clear the mandatory field at the time of cloning the issues. 

For this i can create an automation which only copy those value which user want to retain, but mandatory field what I am thinking to set value N/A. But this will force user to change the mandatory field value. 

Kindly suggest what would be best approach to clear mandatory field at the time of cloning and asking to fill those mandatory field after cloning. 

[Christos Markoulatos]

Hi @Vikrant Yadav,

Thinking about your approaches, i think using automation to copy only the fields you want to retain makes sense, and your thought about setting N/A for mandatory fields could work, but it does feel like a workaround unless you add validators to force users to change it later.

What I think u should do is simply clear those mandatory fields after cloning so they’re blank. This way, Jira’s built in required field logic does the heavy lifting and prompts the user to fill them in when they edit or transition the issue. It keeps things cleaner than using placeholders and avoids the risk of someone leaving N/A in there. If the field is required on the Create screen, you can also use a custom screen for the clone process or add a validator on the next transition to make sure the user updates it.

Try it and let me know, its a interesting case!

[Vikrant Yadav]

Hi @Christos Markoulatos  As these field mandatory field on Create Screen, Automation won't be clone the issue until I fill the mandatory field. 

Can I clean mandatory field after cloning or Cloning an issues via automation does automation able to create the without filling any data in mandatory field? 

[Christos Markoulatos]

Hi @Vikrant Yadav,

You are absolutely correct and now that I think it more, if those fields are mandatory on the Create screen, Jira’s native Clone action (or even automation using “Clone issue”) will fail unless those fields are populated. Automation doesn’t bypass required fields during creation because it uses the same validation rules as the UI.

My next thoughts:

• Option 1: Temporarily set a placeholder (like N/A) during cloning, then immediately clear those fields in a second automation rule. This way, the issue gets created successfully, and the fields are blank for the user to fill later.
• Option 2: Use a custom screen for the Clone transition that excludes those mandatory fields, so Jira doesn’t enforce them during the clone process.

Personally, I’d go with Option 1 because it’s the simplest to implement with automation and doesn’t require workflow changes.

What do u think?

[Vikrant Yadav]

@Christos Markoulatos  Second automation won't clear the field as it's mandatory field 

give error : PAA-12055 (Dev is required. (customfield_10058)) 

[Christos Markoulatos]

@Vikrant Yadav you are right i didn't think it through, apologies!

what about: Clone into an Intake issue type (or project) mapped to a field configuration where Dev isn’t required, then gate the move to the “real” workflow with a validator that demands Dev?