Moving tickets from one project into another bypassing the required field checks. We have required fields A and B, etc. Here field A has some condition validators ie if A has some specific field value , other fields B, C are required. But when we are moving from project to another project , the A field is not showing, its showing B only and that is mandatory field.
You mention nested conditions, i.e. "if field A has value X, then field B is required", this is not Jira's out of box setting, so you are likely using a 3rd party plugin allowing you to set up these nested conditions.
This should, theoretically (not that it's documented as a proof), depend on which fields are marked as required in Field Configuration for that Issue Type, in that destination project. Can you check that and see which fields are set as required? Then this should correspond to the field you see on the Move page.
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