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

Cloning issue ignoring required fields

unknown

I can create an issue without filling custom required field (e.g. "Field 1") using "Clone" button on old issue that have been created earlier than the "Field 1" was added.

Jira does not indicate that the are any errors caused by a required field.

Is it OK? How do I able to fill all required fields while cloning an old issue, not to just edit the new created issue?

We have JIRA v7.9.0

Thanks

Accepted answers

Nic Brough -Adaptavist-

Yes, that is correct - a clone is an exact copy of the current issue (barring the unique id). It takes the issue as it currently is.

John Funk

Hi Julia,

One thing to do might be to review all of the issues that have already been created and are missing the required field. Then you can get those all updated and the cloned issue will always have the required information. :-)

All comments

Nic Brough -Adaptavist-

Yes, that is correct - a clone is an exact copy of the current issue (barring the unique id). It takes the issue as it currently is.

John Funk

Hi Julia,

unknown

Hi,

This way still doesn't look easy, but thanks

unknown

Thank you

jing_guo

Hi Julia,

have you resolved the clone issue with the required fields checking?

would you like to share it? I am facing the same issue

Thanks.

Jing

unknown

Hi Jing,

Unfortunately I haven't. We clone issue and then fill in the required fields.

Jarrod Moura_ebyoek

Hi guys,

The way I sorted this out was put a screen on the transition in the workflow. The field configuration will then ensure that these naughty people capture these required fields.

I didn't want to use an external plugin to do this and just wanted to use core Jira functionality.

Whitni Smith_dtxmgr

adding to this, using screens and workflow validators are the best route to ensure necessary fields get filled out, even if they aren't required globally but project wise.

I used a workflow transition with a screen and workflow validators that triggered an automation rule to clone (or create new) ticket when it transitioned.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

clone