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 ?
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.
Hi @Hana Kučerová ,
Thanks for your reply. The transition solution is not an option. That will imply putting the validator in each possible transition of the different workflows.
Bulk update is ok when you have limited options for the values and very few custom fields impacted. But that's not the case.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events