Hi Community,
I tried searching for a solution, but couldm't find a clear instruction on how to solve my problem. Hopefully you can help me out.
I've been following this guide, to copy an Epic, with underlying user stories.
In the basics this works fine, but the moment I try to copy the field "acceptance criteria", which apparently is a custom checklist field, the automation gives an error.
Error:
"Onbekende velden ingesteld tijdens het klonen. Mogelijk zijn deze niet beschikbaar voor het project/type. Controleer de configuratie van je aangepaste velden. Velden genegeerd:
The admin was not sure if it is an add on. But, I could find a link in the submenu, that states "herocoders". According to their documentation, it should be possible.
I found the following information, that a few settings should be applied first, before cloning is possible through automation:
Ensure the save local checklist items to jira custom fields global setting is enabled.
Ensure the Checklist Text field is included on the "Create issue screen"
I asked my admin to check this out, but they have trouble adding the field to the "Create issue screen".
Hi @Vries_ E_ de _Elske_ and welcome to the community!
If you are willing to use a third-party app you can try our app, Deep Clone for Jira.
Deep Clone is compatible with lots of other apps, and you can find a list of compatible apps here. The app you are using for your checklists might be in there. If not you can try anyway and if it doesn't work you can contact us, and we might be able to find a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vries_ E_ de _Elske_ -- Welcome to the Atlassian Community!
Are you using a marketplace addon / app for checklists or the built-in checklist field?
If you are using a marketplace one, each is different in how they are implemented. I recommend checking the vendor's documentation for how to copy the checklist field.
Additionally, that error seems to indicate the checklist custom field is not available for the child issue type. Have you confirmed if it is configured for the field?
Kind regards,
Bill
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.