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 :)
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. :-)
Hi,
This way still doesn't look easy, but thanks =)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you =)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jing,
Unfortunately I haven't. We clone issue and then fill in the required fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.