Would somebody have an explanation regarding the custom fields to be documented when we move an issue ? In fact, there are just some custom fields suggested randomly when we move the issue and not all of them. Is it normal? could we configure and change that? if yes, could you please tell me how?
thanks in advance
It's definitely not "random". It's stopping you from breaking your data by validating what you are putting in.
Check the field configuration schemes for the source and target project - you'll find that in most cases, your "random" fields are optional in the source, and mandatory in the target. That's the configuration side of it - you can't change the "move" option, it's just stopping you from breaking your data.
thanks for your answers. Before asking, I had checked the fields configuration and the potential validators in the workflow but none of the fields suggested when I move an issue are mandatory or required. That's why i let myself to qualify them as "random".
I'm really sorry, I forgot the other parts. 1) Are the fields different in the field configurations in *any* way? Mandatory, you've already done, but shown/hidden is the other question? (Renderer doesn't matter) 2) Could you check the custom field *contexts* too? Are they different for the project/issuetypes being moved between?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs