Moving issues from One project to another. Target has required fields that Source has not

Kamel Meftah_ni7grf

Hi there

We are in the process of migrating a NexGen project to Jira classic. In the classic (target) project there are a bunch of required fields. Those fields are not necessarily filled out in source project. When doing the migration via bulk move, Jira asks for the fields to be filled out. We are talking about hundreds of issues. So I changed the Field configuration in the target to deactivate all the required fields. Migration goes smoothly. But after reimplementing the original Custom field configuration on target, I was expecting Jira to ask users to provide missing fields at the next transition. Unfortunately it's not the case. What should be the approach ?

 

Thanks

Hana Kučerová

Hi @Kamel Meftah ,

your users won't probably be able to edit and save these issues without adding all the mandatory fields filled, but they won't be forced to do it during transition.

If you want to forced them to add the values during transition, you can temporary add screen with all the necessary fields to the transition.

The second option I can see it to do some sort of bulk updates of your issues.