nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Move an issue : random custom fields to be updated

mel vega

Hi,

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

Melissa

Accepted answers

unknown

It happened to me when the custom field is required in the target issue type and it's not in the source issue type so JIRA ask you to put values to it. Check that.

All comments

unknown

It happened to me when the custom field is required in the target issue type and it's not in the source issue type so JIRA ask you to put values to it. Check that.

Nic Brough -Adaptavist-

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.

mel vega

hi,

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".

Thanks

Melissa

Nic Brough -Adaptavist-

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jira-core